-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Are Pod and Service operations are no longer PropagationPolicyConfigurable? #2745
Closed
milosonator opened this issue
Jan 22, 2021
· 1 comment
· Fixed by #2814 or jenkinsci/kubernetes-client-api-plugin#83
Closed
Are Pod and Service operations are no longer PropagationPolicyConfigurable? #2745
milosonator opened this issue
Jan 22, 2021
· 1 comment
· Fixed by #2814 or jenkinsci/kubernetes-client-api-plugin#83
Labels
Comments
Apologies for this. I think it affects all resources not just Pod and Service. both ServiceList svcList = kubernetesClient.services()
.inNamespace("myNameSpace")
.withLabel("myLabel")
.list();
kubernetesClient.resourceList(svcList)
.inNamespace("myNameSpace")
.withPropagationPolicy(DeletionPropagation.BACKGROUND)
.delete(); |
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Feb 15, 2021
11 tasks
manusa
pushed a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Feb 16, 2021
manusa
pushed a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Feb 16, 2021
manusa
pushed a commit
that referenced
this issue
Feb 16, 2021
This was referenced Mar 12, 2021
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrading from 4.9.0 to 4.13.10, I find the following code no longer working:
However, I can't call
withPropagationPolicy
on this operation. Is this no longer supported, or did this not make sense to begin with, and was therefore removed? If no, how can I ensure I can set the propagation behavior for this delete operation?Is it no longer there because the delete can't cascade to anything since Pods and Services don't have any dependents? Any help much appreciated.
The text was updated successfully, but these errors were encountered: