Skip to content
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

Requirement to have write access to kube-system namespace #74

Open
waza-ari opened this issue Sep 20, 2024 · 0 comments
Open

Requirement to have write access to kube-system namespace #74

waza-ari opened this issue Sep 20, 2024 · 0 comments

Comments

@waza-ari
Copy link

Hi,

first of all, thanks for providing this amazing project! I'm installing it to a new cluster via ArgoCD, which essentially requires to specify which namespaces a certain project has access to. Typically, a project is constrained to the namespace(s) it requires. Nginx Ingress and cert-manager are there already, however your Helm chart installs one specific RoleBinding in the cube-system namespace:

There are some scenarios in GKE where the kube-system namespace is completely protected (see https://cert-manager.io/docs/installation/compatibility/ for example), and it seems like a good idea in general.

I'm wondering why this permission is required, could you provide any details? If its not strictly necessary, would it be possible to at least allow disabling it via helm chart values?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant