Skip to main content
Version: main 🚧

Service accounts

Supported Configurations
Running the control plane as a container with:

By default, this is disabled.

Sync ServiceAccount resources from the cluster to the control plane cluster.

This is useful for using AWS IAM roles for service accounts with the cluster. In this scenario, the control plane cluster is defined as the identity provider to access your OIDC-compatible system, which means you don't have to configure each cluster as a provider. vCluster creates a control plane cluster ServiceAccount token for your synchronized ServiceAccount from the cluster.

Synced ServiceAccount names are rewritten

vCluster renames the ServiceAccount when it syncs it into the vCluster control plane's namespace, to NAME-x-NAMESPACE-x-VCLUSTER_NAME. vCluster truncates rewritten names longer than 63 characters and appends a hash suffix. Cloud IAM trust policies must reference the rewritten name, so build it with the Platform API rather than hard-coding it.

With namespace syncing enabled, a ServiceAccount in a mapped namespace keeps its original name and only its namespace changes.

See Resource name length and truncation for the rule, and Integrate EKS Pod Identity with vCluster for a worked example.

Sync ServiceAccounts from the tenant to control plane cluster​

sync:
toHost:
serviceAccounts:
enabled: true

Config reference​

For every field under sync.toHost.serviceAccounts, see the sync reference.