Replies: 3 comments
-
Observed a similar issue here and we also needed to manually deploy a 'fix' to get the chart to work, apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: role-creator
rules:
- apiGroups:
- rbac.authorization.k8s.io
resources:
- roles
verbs:
- create
- delete
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: role-creator-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: role-creator
subjects:
- kind: ServiceAccount
name: actions-runner-scale-set-controller-gha-rs-controller
namespace: actions-scale-set |
Beta Was this translation helpful? Give feedback.
0 replies
-
FYI I got around this issue using Kustomize, this just allows me to override the cluster role RBAC until the bug is resolved but keep the changes in our code base.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My controller pod was having issues with being able to create
roles
androlebindings
in the arc-runners namespace. It also had issues reading the kubernetes secret used by the runners inarc-runner
Examples:
Version running:
No custom settings inside values.yaml
I got it working with the following changes to RBAC:
Added the following verbs
to the following
resources
I also had to add
I did not test how restrictive I could make the RBAC rules, and I thought to create a PR for these changes but wanted to reach out and see if others had the same issue as it may be a configuration error on my side. The more I thought about it though the controller is supposed to stand up listeners, and it can't create runners/listeners with out the ability to create. It also can't use the k8s secret for the runners unless it has the ability to view secrets.
Let me know if others have the same problem, if so I'll make a PR to reflect the changes I had to make. Thank you
Beta Was this translation helpful? Give feedback.
All reactions