Fix .Values scoping issue in namespaced-role.yaml

[dac73]

Description

This PR addresses a scoping issue in the namespaced-role.yaml Helm template, where .Values could not be evaluated due to the context being overridden inside a range loop. The error encountered during the Helm upgrade was:

template: mirrord-operator/templates/namespaced-role.yaml:9:24: executing “mirrord-operator/templates/namespaced-role.yaml” at <.Values.role>: can’t evaluate field Values in type interface {}

Root Cause

The range loop changes the context (.) to the current item being iterated (a namespace in roleNamespaces). As a result, .Values could not be accessed directly.

Proposed Fix

• Use $ to explicitly refer to the top-level context for accessing .Values and for calling nested templates like labels and rules.
• Ensure consistent access to .Values throughout the template.

---

Changes Made

• Updated namespaced-role.yaml to use $ for referencing the top-level context.
• Preserved compatibility with existing values.yaml configurations.

---

References

• Original issue: .Values scoping error during Helm upgrade.

[aviramha]

Thanks for the contribution! Do you mind adding the test case to test_values directory?

[dac73]

@aviramha operator_role_labels.yaml should cover this change already. Reason for adding this change is that version 1.11.0 fails with: template: mirrord-operator/templates/namespaced-role.yaml:9:24: executing “mirrord-operator/templates/namespaced-role.yaml” at <.Values.role>: can’t evaluate field Values in type interface {}
Will add another test.

[aviramha]

Thank you!