-
Notifications
You must be signed in to change notification settings - Fork 56
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
Fix issues with imagePullSecret handling #898
Conversation
Restrict secret list when checking for imagePullSecrets to only the current workspace's namespace. Signed-off-by: Angel Misevski <amisevsk@redhat.com>
ImagePullSecrets are not read from the cluster in a consistent order. This can result in unnecessarily updating the workspace deployment to change the order of imagePullSecrets, triggering rollouts and restarting pods. Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
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.
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amisevsk, AObuchow, dkwon17 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What does this PR do?
Fixes a couple of issues with how DWO handles imagePullSecrets:
What issues does this PR fix or reference?
Closes #896
Closes #897
Is it tested? How?
Test that issues #896 and #897 no longer reproduce.
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-path
to trigger)v8-devworkspace-operator-e2e
: DevWorkspace e2e testv8-che-happy-path
: Happy path for verification integration with Che