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

ServiceAccount missing permissions to list ClusterOriginIssuer resources #130

Closed
xorinzor opened this issue Jul 9, 2024 · 2 comments · Fixed by #131
Closed

ServiceAccount missing permissions to list ClusterOriginIssuer resources #130

xorinzor opened this issue Jul 9, 2024 · 2 comments · Fixed by #131

Comments

@xorinzor
Copy link
Contributor

xorinzor commented Jul 9, 2024

After updating to 0.9.0 and creating a ClusterOriginIssuer my pod is throwing this error:

W0709 20:16:22.501014       1 reflector.go:539] pkg/mod/k8s.io/client-go@v0.29.0/tools/cache/reflector.go:229: failed to list *v1.ClusterOriginIssuer: clusteroriginissuers.cert-manager.k8s.cloudflare.com is forbidden: User "system:serviceaccount:cloudflare-origin-ca-issuer:cloudflare-origin-ca-issuer" cannot list resource "clusteroriginissuers" in API group "cert-manager.k8s.cloudflare.com" at the cluster scope
E0709 20:16:22.501074       1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.29.0/tools/cache/reflector.go:229: Failed to watch *v1.ClusterOriginIssuer: failed to list *v1.ClusterOriginIssuer: clusteroriginissuers.cert-manager.k8s.cloudflare.com is forbidden: User "system:serviceaccount:cloudflare-origin-ca-issuer:cloudflare-origin-ca-issuer" cannot list resource "clusteroriginissuers" in API group "cert-manager.k8s.cloudflare.com" at the cluster scope

Deleting the ServiceAccount and letting Helm recreate it doesn't fix the problem.

Relates to #125

@terinjokes
Copy link
Contributor

The non-Helm RBAC files got updated, but they got missed for Helm. We don't use Helm, so easy for us to miss.

@xorinzor
Copy link
Contributor Author

xorinzor commented Jul 9, 2024

No worries, I appreciate the quick response & fix; Thanks!

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

Successfully merging a pull request may close this issue.

2 participants