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
{{ message }}
This repository has been archived by the owner on Feb 12, 2021. It is now read-only.
Hi, I am using kubernetes with CoreOS. I have read the documentation but still some doubts about the correct way of documentation.
I am using etcd and want to be in safe in case a reboot. At the same time I want to disable updates too. Since I am very often creating our infrastructure from bottom up, I want an immutable infrastructure instead of updating it.
What I understood is that in order to have a healthy reboot I need:
reboot_strategy: etcd-lock
and in order to disable updates I need:
- name: update-engine.service
mask: true
If my approach is true, It would be nice to add a documentation to make it clear.
What do you think?
The text was updated successfully, but these errors were encountered:
The correct way to do this is to use Ignition to mask both locksmith and update engine. I realize that in your case, @cemo, you are unable to use Ignition.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I am using kubernetes with CoreOS. I have read the documentation but still some doubts about the correct way of documentation.
I am using etcd and want to be in safe in case a reboot. At the same time I want to disable updates too. Since I am very often creating our infrastructure from bottom up, I want an immutable infrastructure instead of updating it.
What I understood is that in order to have a healthy reboot I need:
and in order to disable updates I need:
If my approach is true, It would be nice to add a documentation to make it clear.
What do you think?
The text was updated successfully, but these errors were encountered: