-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Avoid reboots in select cases #28090
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@yuqi-zhang Would you be the best person to review these doc changes? |
yuqi-zhang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally I think we should specify that these are explicitly 4.7 specifically (or maybe implied is good enough?) and that they still disrupt your workloads due to the drain action. There just won't be a physical reboot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we should specify specifically that:
- as of 4.7, this change will no longer trigger a reboot (if no other changes were applied at the same time)
- it will instead drain the nodes, apply the changes and reload crio.service on the host, and then uncordon
- the
/host/etc/containers/registries.confis a bit odd, it should just be/etc/containers/registries.confon the actual hosts. The only time you would see if in/host...is if you have a container that mounted the system root to/host(e.g. a debug container)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe should specify as of 4.7, this will not reboot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... e.g. ICSP changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yuqi-zhang Thanks for the comments.
What is ICSP? ImageContentSourcePolicy?
We don't use that acronym in the docs apparently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry that would be imageContentSourcePolicy, e.g. here: https://docs.openshift.com/container-platform/4.6/updating/updating-restricted-network-cluster.html#images-configuration-registry-mirror_updating-restricted-network-cluster
i.e. if you create/update an imagecontentsourcepolicy object, it gets populated into a machineconfig. This was one of the asks from customers so I thought it might have made sense to explicitly list it here. I defer to your judgement on that though.
|
Check reference in images-configuration-file.adoc |
modules/machine-config-overview.adoc
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed typo
|
lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed typo
ed925d8 to
7aa09a6
Compare
|
The preview will be available shortly at: |
7aa09a6 to
83ca275
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestions since this content was already in place :)
s/Machine Config Operator/Machine Config Operator (MCO)
s/CA/certificate authority (CA)
|
I left a couple of small suggestions, otherwise LGTM! |
83ca275 to
6497751
Compare
|
/cherrypick enterprise-4.7 |
|
@mburke5678: new pull request created: #28251 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Adding MCO behavior changes from #28090
…-28388-to-enterprise-4.7 [enterprise-4.7] Adding MCO behavior changes from #28090
https://issues.redhat.com/browse/OSDOCS-1645