-
Notifications
You must be signed in to change notification settings - Fork 1.9k
How to clear cache after pruning images #17959
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
|
The preview will be available shortly at: |
|
@adambkaplan @wking PTAL |
modules/pruning-images.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.
@adambkaplan When would the use reset to false?
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.
@adambkaplan ^^
modules/pruning-images.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.
nit: oc patch ... so you don't have to list the unrelated stuff like proxy settings?
modules/pruning-images.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.
nit: do we want to remove this for master? I thought this would work, and still be preferred, for 4.3+. But I'm unfamiliar with the registry internals.
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.
@wking this was from 3.x. OpenShift 4 has completely different namings for the deployment
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.
@wking I was planning to merge this PR to master and cherrypick to 4.1 and 4.2 for now. Then merge https://github.com/openshift/openshift-docs/pull/17966/files to master when 4.3 is ready to go. The 4.3 PR has: $ oc rollout restart deployment/image-registry -n openshift-image-registry
|
@mburke5678 @wking I did the following to confirm that the following will work: For 4.3 - For 4.2 and 4.1 - |
|
That said, the reason this works cleanly is because of a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1769927 These commands can force up to two rollouts on other operator-controlled deployments - one that adds the restart annotation, and a second rollout that the operator initiates to remove the annotation. Is the race that may trigger two rollouts something we should worry about (ex - for ocm or the apiservers)? |
|
@adambkaplan Is the |
|
@tnozicka is this the correct command upstream? Do we need to file a BZ? |
1 similar comment
|
@tnozicka is this the correct command upstream? Do we need to file a BZ? |
|
yes, file a BZ to wire it |
|
assign the BZ to me, fyi the fix is here openshift/oc#169 |
836e5f3 to
4b59d22
Compare
|
/cherrypick enterprise-4.1 |
|
@mburke5678: new pull request created: #18373 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.2 |
|
@mburke5678: new pull request created: #18374 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. |
https://bugzilla.redhat.com/show_bug.cgi?id=1730148
Per Slack: https://coreos.slack.com/archives/CEKNRGF25/p1573081260097100?thread_ts=1573079169.094900&cid=CEKNRGF25