You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using an existing ServiceAccount with Headlamp Helm chart
Issue
When deploying Headlamp in environments where ServiceAccounts and RBAC are managed externally (e.g., through a platform team or GitOps process), I need to configure Headlamp to use an existing ServiceAccount instead of creating a new one.
Current configuration
The Headlamp Helm chart creates a new ServiceAccount by default:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Using an existing ServiceAccount with Headlamp Helm chart
Issue
When deploying Headlamp in environments where ServiceAccounts and RBAC are managed externally (e.g., through a platform team or GitOps process), I need to configure Headlamp to use an existing ServiceAccount instead of creating a new one.
Current configuration
The Headlamp Helm chart creates a new ServiceAccount by default:
And it also creates a ClusterRoleBinding to grant the ServiceAccount access:
Desired configuration
I want to use an existing ServiceAccount (e.g.,
a-support
) that already has appropriate RBAC bindings.Questions
Beta Was this translation helpful? Give feedback.
All reactions