-
Notifications
You must be signed in to change notification settings - Fork 79
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
[openstackclient] Store hash to determine when pod spec changes #1211
[openstackclient] Store hash to determine when pod spec changes #1211
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olliewalsh 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 |
/hold |
65c93f8
to
fba9c3a
Compare
/test openstack-operator-build-deploy-kuttl |
1 similar comment
/test openstack-operator-build-deploy-kuttl |
202d0f4
to
73dfdc9
Compare
/remove-hold |
/cherry-pick 18.0-fr1 |
@olliewalsh: once the present PR merges, I will cherry-pick it on top of In 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-sigs/prow repository. |
73dfdc9
to
1f1eb2c
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
Comparing the desired pod spec to the current pod spec is not reliable as the spec can be mutated by k8s e.g to add volume mount for a service account or to add the default nodeselector from the namespace/cluster on OpenShift Instead store a hash of the original pod spec and compare this to the hash of the current desired pod spec to determine if the spec has changed.
1f1eb2c
to
eaa330c
Compare
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/11995a064bad41f5af6c7be36a64e518 ❌ openstack-k8s-operators-content-provider NODE_FAILURE Node request 100-0007693715 failed in 0s |
recheck |
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.
lgtm
/test openstack-operator-build-deploy-kuttl |
3 similar comments
/test openstack-operator-build-deploy-kuttl |
/test openstack-operator-build-deploy-kuttl |
/test openstack-operator-build-deploy-kuttl |
eba4d82
into
openstack-k8s-operators:main
@olliewalsh: #1211 failed to apply on top of branch "18.0-fr1":
In 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-sigs/prow repository. |
Comparing the desired pod spec to the current pod spec is not reliable as
the spec can be mutated by k8s e.g to add volume mount for a service account
or to add the default nodeselector from the namespace/cluster on OpenShift
Instead store a hash of the original pod spec and compare this to the hash
of the current desired pod spec to determine if the spec has changed.
Resolves: OSPRH-11701