kubernetes-retired / multi-tenancy

A working place for multi-tenancy related proposals and prototypes.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Remove HNC managed labels - convert HNC namespace to normal namespace

jvaibhav123 opened this issue · comments

Hi,

We made a mistake in production for one of the namespace which shoudn't be HNC.
Currently we see all HNC labels on that namespace. When we trying to delete HNC labels, namespace validation webhook is denying that request. We added exclude-namspace argument and added label "hnc.x-k8s.io/excluded-namespace=true" to namespace. I think this will make sure this namespace is not managed by HNC however we would like to get rid of HNC labels.

Is there a way to do that?

Thanks in advance.

Regards,
Vaibhav Joshi

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Sorry I missed this. Are you saying that even though the namespace has been excluded, there are still HNC labels on it which you can't remove after having excluded the namespace? That shouldn't happen - if you're still seeing this, can you please include the exact command you wrote, the result of kubectl get namespace <name> -oyaml and the result of trying to remove the labels? Thanks!

Repo is to be archived - see kubernetes/org#4297 for details

/close

@mrbobbytables: Closing this issue.

In response to this:

Repo is to be archived - see kubernetes/org#4297 for details

/close

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/test-infra repository.