Better documentation on supervisor updating and DNS handling is needed

So I’ve recently suffered from the CoreDNS issue nuking my local DNS server configuration (I logged an issue against hassos here). I acknowledge the great and rapid response by the hassio team. But through this experience, I learnt some things that surprised me. I think they are issues and should be addressed somehow.

Firstly: I had no idea that the supervisor is auto-upgraded. This is all kinds of wrong:

• I decide when to upgrade hassio / hassos and home assistant. I wait for others to try new major releases and wait for evidence of stability. I wait until I am home and can fix stuff if it breaks
• The supervisor is the only component of hassio that is auto-upgraded. This means that if I choose not to update home assistant or hassio / hassos, supervisor can get ahead, creating conflicts
• The auto-upgrading behaviour of supervisor is not (as far as I can tell) documented anywhere. That’s not cool. At the very least, I should know what to expect.

Secondly: I now have no idea how I am supposed to configure a local DNS server.

• The HassOS guide implies that NetworkManager config is the way to go, but - in my case at least - that is now getting nuked by CoreDNS.
• I can’t find any documentation to tell me whether NetworkManager config getting toasted is by design or is a bug (none of the current issues / PRs suggest to me that it is a bug).
• In fact, I can’t find any documentation about CoreDNS or the CLI hassio dns command set.

I realise that my issue may come across as a rant, but this particularly experience is out of character with what I have come to expect from my 18 months of life with home assistant. Documentation is usually sufficient (if a little terse) and release notes are very clear and solid. I know what to expect and if something breaks it is because I did something stupid. But in this case, something broke, I hadn’t touched anything, and I had no idea where to look. Like many people, I lost most of a day trying to figure it out.

I would be happy to contribute documentation on these two points, but I am completely in the dark as to what is expected. In an otherwise awesome project, this needs fixing.

[SiliconAvatar]

@ntompson, 100% agreed.

As I see it, 3 major changes are needed to make this whole endeavor “mature”, or at least not mickey mouse.

There needs to be a review process before major changes such as this. Similar to the Architecture repo for HA. This would allow the community to vet the validity and possible side effects of such a change.

HassIO Supervisor upgrades need to have changelogs with possible breaking changes same as standard HA releases.

And lastly, and most importantly, HassIO Supervisor releases can not, and should not, EVER auto-update. This should be an opt-in process to automatically update, and allow users to update when they desire. There should never be a situation where system breaks itself and all integrations without any user intervention. This latest issue revealed major point of fragility for this entire platform.

[michalszymura]

It’s especially annoying when you run hassio supervisor on something like unraid, as it stops the container and basically does nothing, making the home assistant non functional until I manually update to the newest version. Being able to disable autoupdates is a must.