[bitnami/contour] Missing ConfigMap and BackendTLSPolicy permissions in clusterrole when adding gatewayRef
Name and Version
bitnami/contour 17.0.5
What architecture are you using?
amd64
What steps will reproduce the bug?
- Add gateway.gatewayRef in contour configmap
- Restart contour
- On startup it it logs the following errors:
level=error msg="pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:229: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps is forbidden: User \"system:serviceaccount:contour:contour-contour\" cannot list resource \"configmaps\" in API group \"\" at the cluster scope" caller="reflector.go:147" context=kubernetes error="<nil>"
level=error msg="pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:229: Failed to watch *v1alpha2.BackendTLSPolicy: failed to list *v1alpha2.BackendTLSPolicy: backendtlspolicies.gateway.networking.k8s.io is forbidden: User \"system:serviceaccount:contour:contour-contour\" cannot list resource \"backendtlspolicies\" in API group \"gateway.networking.k8s.io\" at the cluster scope" caller="reflector.go:147" context=kubernetes error="<nil>"
Are you using any custom parameters or values?
No response
What is the expected behavior?
The chart should add all relevant permissions in rbacs, including those for CRDs.
What do you see instead?
The clusterrole doesn't define permissions for all GatewayAPI crds, namely backendpolicies isn't added. The list and watch permissions on configmaps were also missing, which only throws an error after adding gatewayRef.
Additional information
No response
The clusterrole doesn't define permissions for all GatewayAPI crds, namely backendpolicies isn't added. The list and watch permissions on configmaps were also missing, which only throws an error after adding gatewayRef.
Hi,
Thank you for reporting the issue. As you have identified the issue, would you like to contribute? You can do so by following our contributing guidelines. You'll need to edit the rbac.yaml file and it will benefit the entire community.
Thanks
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Looks like it's been added in chart v17.0.7 Many thanks ❤️