Describe the bug
Being explicit with the ClusterRole is a bit confusing with the example provided since the new 2.12.0 version dropped:
https://github.com/mittwald/kubernetes-replicator?tab=readme-ov-file#role-and-rolebinding-replication
The new version is calling for a nested privileges key under privileges, which the example does not provide:
https://github.com/mittwald/kubernetes-replicator/pull/376/files#diff-baeb807c1cd0802a771e93f056dd25d71609023ea954b189fb0453e60432400aR58
i.e.
serviceAccount:
create: true
annotations: {}
name:
privileges:
- apiGroups: [ "" ]
resources: [ "secrets" ]
privileges: [ "get", "watch", "list", "create", "update", "patch", "delete" ]
To Reproduce
If I use the example as noted here: https://github.com/mittwald/kubernetes-replicator?tab=readme-ov-file#role-and-rolebinding-replication, then helm template fails to parse:
helm template . --values ./values-override.yaml
Error: YAML parse error on kubernetes-replicator/templates/rbac.yaml: error converting YAML to JSON: yaml: line 70: could not find expected ':'
Expected behavior
Expect parsing to work with the proper Rules for an explicit ClusterRole
Environment:
- Kubernetes version: 1.19
- kubernetes-replicator version:
2.11.1 to 2.12.0
Additional context
I assume the example just needs to be updated or maybe you need to make a code change for values.yaml along with templates/rbac.yaml