fix: role binding ref name reference change.

[Greyeye]

1. change roleRef.name to use variable

[github-actions]

Temporary image deleted.

[zapier-sre-bot]

Mergecat's Review

Click to read mergecats review!

😼 Mergecat review of charts/kubechecks/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v2
 name: kubechecks
 description: A Helm chart for kubechecks
-version: 0.5.1
+version: 0.5.2
 type: application
 maintainers:
   - name: zapier

Feedback & Suggestions: The version bump from 0.5.1 to 0.5.2 is appropriate if there are backward-compatible bug fixes or minor improvements. Ensure that the changes in the codebase reflect this version update. 📈

---

😼 Mergecat review of charts/kubechecks/templates/rolebinding.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: {{ .Values.argocd.namespace }}
 roleRef:
   kind: Role
-  name: kubechecks
+  name: {{ include "kubechecks.fullname" . }}
   apiGroup: rbac.authorization.k8s.io
 subjects:
   - kind: ServiceAccount

Feedback & Suggestions:

• 🛡️ Security Consideration: Ensure that the {{ include "kubechecks.fullname" . }} template function resolves to the correct role name. If the role name is dynamic, verify that it does not inadvertently escalate privileges by binding to a more privileged role than intended.

• 🔍 Consistency Check: Double-check that the {{ include "kubechecks.fullname" . }} is consistent with the role name defined elsewhere in your configuration. This helps avoid runtime errors due to mismatched names.

• 📄 Documentation: Consider documenting the rationale for using {{ include "kubechecks.fullname" . }} for the role name. This can help future maintainers understand the change and its context.

---

---

Dependency Review

Click to read mergecats review!

No suggestions found