kubernetes: add sysext documentation #338
Conversation
| :warning: To ease the reading, we voluntarily omitted the checksums of the downloaded artifacts. | ||
|
|
||
| ```yaml | ||
| Here's an example with [butane][butane] to setup a control plane using the Systemd sysext approach or the binaries approach. |
There was a problem hiding this comment.
| Here's an example with [butane][butane] to setup a control plane using the Systemd sysext approach or the binaries approach. | |
| Here are two examples to setup a control plane with [Butane][butane]. The first example is using the systemd-sysext approach to bring in the binaries and update them through systemd-sysupdate. The second approach fetches the binaries but has no way of updating them in-place. |
There was a problem hiding this comment.
The changes are gone because the addition of /etc/sysupdate.kubernetes.d/kubernetes.conf and the force push flushed them^^ https://github.com/flatcar/flatcar-docs/compare/2e44a5af9434779c7172b276b9fd4f4fcd24a398..a3ec8195b004ced01d8b397d82e1400a09b7bcc2
There was a problem hiding this comment.
ah !!! Forgot to rebase before pushing. Thanks for the heads up :D
There was a problem hiding this comment.
Maybe you can get the commit from the reflog or from github :D
| - name: kubernetes.conf | ||
| contents: | | ||
| [Service] | ||
| ExecStartPre=/usr/lib/systemd/systemd-sysupdate -C kubernetes update |
There was a problem hiding this comment.
Should we run refresh here?
There was a problem hiding this comment.
Well, that's still the question of handling the update. We could show in the documentation an example using KureD for example.
Or we can simply run refresh and systemctl restart kubelet but not sure it's the right way to upgrade a Kubernetes node.
There was a problem hiding this comment.
Doing the touch for kured sounds good (maybe an env var can first capture the symlink target, so that the ExecStartPost can compare this).
There was a problem hiding this comment.
Added Kured example with symlink comparison.
There was a problem hiding this comment.
Thanks, that's good :) Any tweaks to how that is done can also be added later.
tormath1
force-pushed
the
tormath1/kubernetes-sysext
branch
2 times, most recently
from
a3ec819 to
168e4b1
Compare
Signed-off-by: Mathieu Tortuyaux <[email protected]>
tormath1
force-pushed
the
tormath1/kubernetes-sysext
branch
from
168e4b1 to
e7ff156
Compare
I tried to make it dynamic using the
tabfeature, defaulting to the Sysext approach.