We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Because of legacy reasons namespaces in addition to .meta.finalizers have also .spec.finalizers. There is also a separate endpoint for the purpose PUT /api/{version}/namespaces/{namespace}/finalize - see https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/namespaces.md#rest-api and kubernetes/kubernetes#77086 (comment).
.meta.finalizers
.spec.finalizers
PUT /api/{version}/namespaces/{namespace}/finalize
k8s.io/client-go has clientset.CoreV1().Namespaces().Finalize(ns) that can finalize namespace.
k8s.io/client-go
clientset.CoreV1().Namespaces().Finalize(ns)
I would be great if controller-runtime client can also perform this action.
The text was updated successfully, but these errors were encountered:
/kind feature
I think we have someone working on generic subresource support, which would bring in this as well.
Sorry, something went wrong.
#172
Ok, then closing this one in favour of #172.
Merge pull request #573 from mengqiy/update_how_to_contribute_doc
a085eb8
update how to deploy kubebuilder book
No branches or pull requests
Because of legacy reasons namespaces in addition to
.meta.finalizers
have also.spec.finalizers
. There is also a separate endpoint for the purposePUT /api/{version}/namespaces/{namespace}/finalize
- see https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/namespaces.md#rest-api and kubernetes/kubernetes#77086 (comment).k8s.io/client-go
hasclientset.CoreV1().Namespaces().Finalize(ns)
that can finalize namespace.I would be great if controller-runtime client can also perform this action.
The text was updated successfully, but these errors were encountered: