-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Adding documentation for updating a disconnected cluster #21993
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
f34c3e0 to
812f370
Compare
|
This doesn't include what I expected to see from #17896 which is the terminology and flow changes (especially the removal of the atrocious registry creation). Is that a follow up I'm missing? 17896 is what the flow should be and captures the flow and terminology that we want to use with customers (I haven't heard a concrete counter). If that's not included here it needs to be a follow up. Our current flow is not correct. |
If that PR gets picked back up and lands, or is carried and lands, I think we'd be happy to rebase on top. But are there any corners we can cut to get something landed around manual ConfigMap creation without having to resolve all the outstanding issues in one big PR? |
|
I was expecting you guys to pick that up and drive it to completion - that was what I thought the last communication on it was. |
3f07318 to
517644f
Compare
|
New changes are detected. LGTM label has been removed. |
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.
@kalexand-rh Command line in the following step 5 missed ${ARCHITECTURE}.
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. Thanks!
Signed-off-by: Lalatendu Mohanty <[email protected]>
|
@jianlinliu, I know this change is valid for 4.5. Which earlier versions can I backport this change to? |
We should backport to 4.4. As this feature is available from 4.4.8. |
|
LGTM |
|
/cherrypick enterprise-4.4 |
|
@kalexand-rh: #21993 failed to apply on top of branch "enterprise-4.4": 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. |
|
/cherrypick enterprise-4.5 |
|
@kalexand-rh: new pull request created: #23429 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. |
|
Per https://bugzilla.redhat.com/show_bug.cgi?id=1828214#c14 and an ongoing discussion on Slack, this change also needs to be ported to 4.3. |
|
@jianlinliu, do you have any objection to applying this change to 4.3? @LalatenduMohanty says fix is in 4.3.12. |
|
This is a big PR. Some pieces of process does not work in 4.3. Such as: oc mirror payload to disk scenario. But 4.3.13 indeed support user manually create signature configmap, then apply it to existing clusters, then trigger disconnected cluster upgrade. |
|
@kalexand-rh For versions in 4.3.z (i.e. after 4.3.12) will not get the the ConfigMap created by the [1] https://docs.openshift.com/container-platform/4.5/updating/updating-restricted-network-cluster.html#update-oc-configmap-signature-verification_updating-restricted-network-cluster |
Fix: asciidoctor: WARNING: includes/update-configuring-image-signature.adoc: line 34: no callout found for <1> from 8a31e17 (Adding documentation for updating a disconnected cluster, 2020-05-08, openshift#21993).
Signed-off-by: Lalatendu Mohanty [email protected]