Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
sometimes we have problems with the worker nodes or network problems, and in the end result the hnc pods are not running (we do use ha),
and since there is this heavy webhook we basically cant do anything on the cluster because it requires to validate almost every api request, thus preventing us from fixing the cluster so we need to delete the webhook and deal with the hnc first.
im not sure why the validation webhook has * but i was wondering isn't its better to run the hnc pods on the master nodes?
then hnc and api can go together, if api is available than probably hnc as well.
In response to [this](https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/352#issuecomment-1987189996):
>Will be fixed by https://github.com/kubernetes-sigs/hierarchical-namespaces/pull/285.
>
>Duplicate of https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/152
>
>/close
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sometimes we have problems with the worker nodes or network problems, and in the end result the hnc pods are not running (we do use ha), and since there is this heavy webhook we basically cant do anything on the cluster because it requires to validate almost every api request, thus preventing us from fixing the cluster so we need to delete the webhook and deal with the hnc first.
im not sure why the validation webhook has
*
but i was wondering isn't its better to run the hnc pods on the master nodes? then hnc and api can go together, if api is available than probably hnc as well.