-
Notifications
You must be signed in to change notification settings - Fork 782
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
ModifySet: all subpaths must be a prefix of the location
value of the mutation
#2892
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Not stale /label mutation |
/remove-lifecycle stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
/remove-lifecycle stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
/remove-lifecycle stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
What steps did you take and what happened:
What did you expect to happen:
Add value "39500" to
spec.securityContext.supplementalGroups
for pods where init container "this-container-must-exist" existsAnything else you would like to add:
I read through some of the other related issues regarding this deny, and understand the general concept of eventual consistency vs infinite looping mutations in the context of Assign mutations. Given that this is a ModifySet, however, I'd expected that the risk would be drastically reduced because I'm checking for the existence of another set object. I haven't seen an example provided which could lead to infinite looping.
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: