Open omaratdgtl opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Description: I'm encountering an issue while attempting to bind an existing namespace to a new subnamespace-anchor resource using the
kubectl hns set
command in our Kubernetes cluster configured with hierarchical-namespaces.First attempt
Steps to Reproduce:
Expected Behavior: HNC creates the subnamespace-anchor and binds it to the existing namespace if:
Actual Behavior: Creating the Subnamespace Anchor while the namespace exists results in exceptions. The process produces the following error messages:
Second attempt
Steps to Reproduce:
Expected Behavior: The
kubectl hns set
command should create/update a subnamespace-anchor resource in the SubnamespaceAnchors CRs after updating the tree.Actual Behavior: The
kubectl hns set
command doesn't create/update a subnamespace-anchor resource in the SubnamespaceAnchors CRs after updating the tree.I ended up going with a dirty workaround attempt:
To address this issue, I attempted the following workaround:
kubectl hns set
command to set an existing namespace to its parent.Result: While this approach resolves cosmetic problems, issues persist with the finalizers when attempting to delete a subnamespace-anchor created in this way.
Question: How can I bind an existing namespace to a new subnamespace-anchor resource? Is there any possibility that the
kubectl hns set
command would update the subnamespace-anchors resources or create them if they don't exist?