Skip to content
This repository has been archived by the owner on Feb 12, 2021. It is now read-only.

Correct way to disable updates #1088

Open
cemo opened this issue May 29, 2017 · 3 comments
Open

Correct way to disable updates #1088

cemo opened this issue May 29, 2017 · 3 comments

Comments

@cemo
Copy link

cemo commented May 29, 2017

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?

@sanmai-NL
Copy link

For me this is unclear as as well. cloud-config docs refer to a differently named key reboot-strategy.

@cemo
Copy link
Author

cemo commented Jun 1, 2017

relevant discussion is at here: coreos/bugs#1982

Current state is buggy, waiting someone to be clear the situation.

@crawford
Copy link
Contributor

crawford commented Jun 2, 2017

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.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants