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

Cluster Scoped CRD doesn't work #70

Open
cchanley2003 opened this issue Nov 3, 2020 · 0 comments
Open

Cluster Scoped CRD doesn't work #70

cchanley2003 opened this issue Nov 3, 2020 · 0 comments

Comments

@cchanley2003
Copy link

cchanley2003 commented Nov 3, 2020

When attempting to use the recommended cluster scoped CRD nothing will deploy. Initial error is that the service account for the install job doesn't work. Looking at the logs I see the following error:

E1103 18:28:32.943432 1 controller.go:135] error syncing 'docker-registry': handler helm-controller: failed to create helm--docker-registry rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding for helm-controller docker-registry: ClusterRoleBinding.rbac.authorization.k8s.io "helm--docker-registry" is invalid: subjects[0].namespace: Required value, handler helm-controller: an empty namespace may not be set when a resource name is provided, requeuing

Believe it is attempting to use the namespace from the HelmChart resource, but because it is cluster scoped no namespace exists.

This is running kubernetes 1.18.6

This is running v0.6.0 of the helm-controller.

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