You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we specify the SERVER, GROUP and MACHINE_ALIAS in /etc/flatcar/update.conf when bootstrapping a node. This makes it quite static as we're not touching/actively managing this file after initial bootstrap.
Impact
At this point there is no way to manage these directives via Kubernetes which forces us to manually change it on the host.
Ideal future situation
Ideally we would be able to set annotations on a node specifying SERVER, GROUP and MACHINE_ALIAS which overrides the directives in /etc/flatcar/update.conf. This would give us a lot of flexibility in controlling which versions run within a cluster. A specific use case I see is running a small set of beta release nodes in a cluster allowing for early detection of issues.
Implementation options
[ Optional: please provide one or more options for implementing the feature requested ]
Additional information
[ Please Add any information that does not fit into any of the above sections here ]
The text was updated successfully, but these errors were encountered:
Current situation
Currently we specify the
SERVER
,GROUP
andMACHINE_ALIAS
in/etc/flatcar/update.conf
when bootstrapping a node. This makes it quite static as we're not touching/actively managing this file after initial bootstrap.Impact
At this point there is no way to manage these directives via Kubernetes which forces us to manually change it on the host.
Ideal future situation
Ideally we would be able to set annotations on a node specifying
SERVER
,GROUP
andMACHINE_ALIAS
which overrides the directives in/etc/flatcar/update.conf
. This would give us a lot of flexibility in controlling which versions run within a cluster. A specific use case I see is running a small set of beta release nodes in a cluster allowing for early detection of issues.Implementation options
[ Optional: please provide one or more options for implementing the feature requested ]
Additional information
[ Please Add any information that does not fit into any of the above sections here ]
The text was updated successfully, but these errors were encountered: