You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: