Andrea Florio

Can you please describe what dependencies you have on the supervisor? In principle the addons are just containers that you can run anywhere and as long as you can call...

Thank you a lot. I'll be looking into those points and see if I can lower the entry bar for you either by providing documentation or even PRs.

All right, so i looked a bit more into it. - the [backup integration](https://www.home-assistant.io/integrations/backup) used to provide backups of the core uses [websockets api](https://developers.home-assistant.io/docs/api/websocket) as can be seen here https://github.com/home-assistant/core/tree/dev/homeassistant/components/backup...

Yes, this is seemgly a small thing but it's incredibly important in the UI in terms of usability. I hope to see this done sooner than later

This worked fine before, but to be honest, the container was also updated recently to a newer version. The same docker-compose was used, just updated the container to a newer...

Thank you, I'll test it

i would like to revive this as it still exists... this is what i have: ``` admin@azure-box:~/Netbox/internal$ kubectl get pod -n netbox -o wide NAME READY STATUS RESTARTS AGE IP...

additional information, if i added podaffinity under "netbox-housekeeping" , that cannot be used. here is values.yml extract ``` affinity: podAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 50 podAffinityTerm: labelSelector: matchExpressions: - key: app.kubernetes.io/component...

> I had issues with the `netbox` and `netbox-worker` pods, but adding these affinity rules to `values.yaml` ensured they both started on the same node: > > ```yaml > affinity:...

> Could you not set the ldap password directly in the `config.yml` of the securityconfig? That is already stored in a secret so should be safe enough for a password....