lambda-controller: ClusterRoleBinding roleRef typo

[gideonmillsfs]

Describe the bug
Mismatch between ClusterRole name and reference in ClusterRoleBinding for namespace cache

Steps to reproduce

1. Modify the <fullname>-namespace-caches ClusterRoleBinding to add a User (with no other bindings) as a subject
2. Assume this user identity
3. Run kubectl get namespaces and observe this error

   Error from server (Forbidden): namespaces is forbidden: User "..." cannot list resource "namespaces" in API group "" at the cluster scope:
   RBAC: clusterrole.rbac.authorization.k8s.io "ack-lambda-controller-lambda-chart-namespace-caches" not found
   

Expected outcome
User is able to list and view namespaces, by being bound to the <fullname>-namespaces-cache ClusterRole

Diagnosis
The ClusterRole is named <fullname>-namespaces-cache, whereas the roleRef in the ClusterRoleBinding points to <fullname>-namespace-caches (note the difference in pluralization).

Environment

• Kubernetes version: 1.31
• Using EKS: yes, eks.32
• AWS service targeted: lambda

[github-actions]

Hello @gideonmillsfs 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[gideonmillsfs]

For the record I'd be happy to fix this myself but company policies make it virtually impossible to contribute to open-source projects.

[knottnt]

@gideonmillsfs A fix for this has been included the 1.8.0 release of the lambda-controller thanks to @vladmalynych!
/close

[ack-prow]

@knottnt: Closing this issue.

In response to this:

@gideonmillsfs A fix for this has been included the 1.8.0 release of the lambda-controller thanks to @vladmalynych!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.