Authentication resources · Kind catalogue · Examples
KubernetesAuthRole¶
API version: auth.openbaoconfig.io/v1alpha1
Scope: Namespaced
Resource: kubernetesauthroles.auth.openbaoconfig.io
Categories: openbao
Example:
spec:
connectionRef:
name: openbao
mountPath: kubernetes
boundServiceAccountNames: [app]
boundServiceAccountNamespaces: [team-a]
tokenPolicies: [app-read]
tokenTTL: 1hExample¶
# Lets pods of ServiceAccount app or app-worker in namespace team-a (or in a namespace selected by labels) log in
# with the openbao audience and get the app-reader policy plus the policy of a Policy resource.
apiVersion: auth.openbaoconfig.io/v1alpha1
kind: KubernetesAuthRole
metadata:
name: app-reader
spec:
connectionRef:
kind: OpenBaoConnection
name: openbao
creationPolicy: CreateOrAdopt
deletionPolicy: Delete
driftDetection: Enabled
mountPath: kubernetes
name: app-reader
boundServiceAccountNames:
- app
- app-worker
boundServiceAccountNamespaces:
- team-a
boundServiceAccountNamespaceSelector:
matchLabels:
tenant: team-a
environment: dev
audience: openbao
aliasNameSource: serviceaccount_name
tokenTTL: 1h
tokenMaxTTL: 4h
tokenExplicitMaxTTL: 8h
tokenPeriod: 30m
tokenPolicies:
- app-reader
policyRefs:
- name: obco-team-a-reader
tokenBoundCIDRs:
- 10.42.0.0/16
- 10.43.0.10
tokenNumUses: 0
tokenType: service
tokenNoDefaultPolicy: false
tokenStrictlyBindIP: false
On GitHub: kubernetesauthrole.yaml, generated sample with every field.
Behaviour and permissions¶
The Kubernetes auth mount and its TokenReview configuration must exist before workloads can log in. This role binds Kubernetes ServiceAccount names and namespaces to OpenBao policies; creating the role does not create those policies or ServiceAccounts.
Use an audience dedicated to OpenBao and configure clients to request that audience. Namespace selectors resolve Kubernetes namespaces; they do not select OpenBao namespaces. The connection and the resource's OpenBao namespace setting determine the target in OpenBao.
Ready confirms that the role matches its spec. It does not validate TokenReview connectivity or a
workload login. Verify authentication using a projected token from the intended ServiceAccount.
Grant read/create/update on auth/<mount>/role/<name>, plus delete when explicitly needed.
The default Orphan retains the role; retaining a role can retain access and requires an explicit
access-revocation process.
Fields¶
Defaults below are CRD schema defaults. A blank cell does not imply zero, false or an empty value; see the field description for omission behaviour. Required fields inside an optional object apply only when that object is set.
| Field | Type | Required | Default | Description | Validation |
|---|---|---|---|---|---|
spec | object | yes | Desired state of a Kubernetes auth role, written to auth/<mountPath>/role/<name>. At least one of boundServiceAccountNamespaces and boundServiceAccountNamespaceSelector is required. | ConstraintsCEL:has(self.mountPath) == has(oldSelf.mountPath) && (!has(self.mountPath) || self.mountPath == oldSelf.mountPath) (mountPath is immutable)CEL: has(self.name) == has(oldSelf.name) && (!has(self.name) || self.name == oldSelf.name) (name is immutable)CEL: has(self.boundServiceAccountNamespaces) || has(self.boundServiceAccountNamespaceSelector) (set boundServiceAccountNamespaces, boundServiceAccountNamespaceSelector or both)CEL: !has(self.tokenTTL) || !has(self.tokenMaxTTL) || duration(self.tokenTTL) <= duration(self.tokenMaxTTL) (tokenTTL must not exceed tokenMaxTTL)CEL: has(self.__namespace__) == has(oldSelf.__namespace__) && (!has(self.__namespace__) || self.__namespace__ == oldSelf.__namespace__) (namespace is immutable)CEL: self.connectionRef == oldSelf.connectionRef (connectionRef is immutable) | |
spec.aliasNameSource | string | no | Value used as the entity alias name of a login: serviceaccount_uid (the ServiceAccount UID) or serviceaccount_name (<namespace>/<name>). OpenBao defaults to serviceaccount_uid. Maps to `alias_name_source`. Example: serviceaccount_name | Constraintsone of:serviceaccount_uid, serviceaccount_name | |
spec.audience | string | no | Audience claim the ServiceAccount JWT must carry. Unset skips the audience check. Maps to `audience`. Example: openbao | Constraintslength: >=1, <=512 | |
spec.boundServiceAccountNames | []string | yes | ServiceAccount names allowed to log in with this role. "*" alone allows every name and cannot be combined with other names. Required. Maps to `bound_service_account_names`. Example: [app, worker] | Constraintsitems: >=1, <=64list type: set CEL: size(self) == 1 || !self.exists(n, n == '*') ('*' cannot be combined with other names)each item: length: >=1, <=253 | |
spec.boundServiceAccountNamespaceSelector | object | no | Label selector for the Kubernetes namespaces allowed to log in, evaluated by OpenBao at login time. OpenBao supports matchLabels only. Maps to `bound_service_account_namespace_selector` (sent as JSON). Example: {matchLabels: {team: a}} | ConstraintsCEL:!has(self.matchExpressions) || size(self.matchExpressions) == 0 (matchExpressions is not supported by OpenBao; use matchLabels) | |
spec.boundServiceAccountNamespaceSelector.matchExpressions | []object | no | Not supported by OpenBao: a selector that sets it is rejected. Use matchLabels. | ||
spec.boundServiceAccountNamespaceSelector.matchExpressions[] | object | no | A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values. | ||
spec.boundServiceAccountNamespaceSelector.matchExpressions[].key | string | yes | key is the label key that the selector applies to. | ||
spec.boundServiceAccountNamespaceSelector.matchExpressions[].operator | string | yes | operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist. | ||
spec.boundServiceAccountNamespaceSelector.matchExpressions[].values | []string | no | values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch. | Constraintslist type: atomic | |
spec.boundServiceAccountNamespaceSelector.matchLabels | map[string]string | yes | Labels a namespace must carry, all of them, to match. Required, at least one. Example: {team: a} | Constraintsproperties: >=1, <=64 | |
spec.boundServiceAccountNamespaces | []string | no | Kubernetes namespaces allowed to log in with this role. "*" alone allows every namespace and cannot be combined with others. A login is allowed when its namespace is listed here or matches boundServiceAccountNamespaceSelector. Maps to `bound_service_account_namespaces`. Example: [team-a, team-b] | Constraintsitems: >=1, <=64list type: set CEL: size(self) == 1 || !self.exists(n, n == '*') ('*' cannot be combined with other namespaces)each item: length: >=1, <=63 | |
spec.connectionRef | object | yes | Connection used to reach and log in to OpenBao. Immutable. | ||
spec.connectionRef.kind | string | no | "OpenBaoConnection" | Kind of the connection: OpenBaoConnection (in the same Kubernetes namespace as this resource) or ClusterOpenBaoConnection (cluster-scoped; its allowedNamespaces must select this namespace). Default: OpenBaoConnection. | Constraintsone of:OpenBaoConnection, ClusterOpenBaoConnection |
spec.connectionRef.name | string | yes | Name of the OpenBaoConnection or ClusterOpenBaoConnection. Example: openbao | Constraintslength: >=1, <=253 | |
spec.creationPolicy | string | no | "Create" | How an object that already exists in OpenBao, and is not yet owned by this resource, is treated. Create (default): create the object; an existing one is refused with reason Conflict. Adopt: take over an existing object and never create one. CreateOrAdopt: create it, or take over an existing one. Settings that always exist in OpenBao (configuration singletons) need Adopt or CreateOrAdopt. | Constraintsone of:Create, Adopt, CreateOrAdopt |
spec.deletionPolicy | string | no | "Orphan" | What happens in OpenBao when this resource is deleted. Orphan (default): the OpenBao object stays. Delete: the object is removed (a configuration singleton is reset to its defaults); data and key holders (mounts, namespaces, KV data, audit devices, endpoints, transit, PKI, SSH CA and TOTP keys, MFA methods, entities) are removed only while the resource carries the annotation openbaoconfig.io/allow-destructive-delete: "true". Kinds whose OpenBao object cannot be deleted reject Delete. | Constraintsone of:Delete, Orphan |
spec.driftDetection | string | no | "Enabled" | Whether OpenBao is re-read periodically to detect and repair out-of-band changes. Enabled (default): re-read every driftInterval. Disabled: write only when the spec or a referenced Secret changes. | Constraintsone of:Enabled, Disabled |
spec.driftInterval | string | no | How often OpenBao is re-read for drift, as a duration of at least 30s. Default: the operator's interval for the kind (15m for kinds that grant access such as policies, auth mounts and roles, 1h for the rest), with jitter. Example: 30m | Constraintslength: <=32CEL: duration(self) >= duration('30s') (driftInterval must be at least 30s) | |
spec.managementPolicy | string | no | "Manage" | Whether the operator writes to OpenBao. Manage (default): converge OpenBao to the spec, create and delete as the policies say. Observe: only read the object and report drift in the conditions; never write or delete. | Constraintsone of:Manage, Observe |
spec.mountPath | string | no | "kubernetes" | Path of the Kubernetes auth method, without the auth/ prefix. Defaults to kubernetes. Immutable. Example: kubernetes/prod-cluster | Constraintspattern:^[A-Za-z0-9_.-]+(/[A-Za-z0-9_.-]+)*$length: >=1, <=128 |
spec.name | string | no | Name of the role in OpenBao, used in the login request. Defaults to metadata.name. Immutable. Example: app | Constraintspattern:^[a-z0-9_]([a-z0-9_.-]*[a-z0-9_])?$length: >=1, <=128 | |
spec.namespace | string | no | OpenBao namespace of the object, relative to the connection's base namespace; empty means the connection namespace itself. Segments are separated by "/", without leading or trailing slash. Immutable: it cannot be added, changed or removed after creation. Example: team-a/apps | Constraintspattern:^[A-Za-z0-9_-][A-Za-z0-9._-]*(/[A-Za-z0-9_-][A-Za-z0-9._-]*)*$length: <=256 | |
spec.policyRefs | []object | no | Policy resources in this Kubernetes namespace whose OpenBao policy names are added to tokenPolicies. The role waits until each Policy is Ready; each Policy must use the same connectionRef and namespace as the role. Example: [{name: app-read}] | Constraintsitems: <=32list type: map (keys: name) | |
spec.policyRefs[] | object | no | Reference by name to an object in the same Kubernetes namespace as this resource. | ||
spec.policyRefs[].name | string | yes | Name of the referenced object, in the same namespace as this resource. Example: my-app | Constraintslength: >=1, <=253 | |
spec.tokenBoundCIDRs | []string | no | Client CIDR blocks or IP addresses allowed to use issued tokens. Unset allows any address. Maps to `token_bound_cidrs`. Example: [10.0.0.0/8, 192.168.1.10] | Constraintsitems: <=64list type: set CEL: self.all(c, isCIDR(c) || isIP(c)) (tokenBoundCIDRs entries must be CIDR blocks or IP addresses)each item: length: <=64 | |
spec.tokenExplicitMaxTTL | string | no | Hard cap on the lifetime of issued tokens that renewals cannot extend, as a duration. Unset or 0 means no explicit cap. Maps to `token_explicit_max_ttl`. Example: 24h | ||
spec.tokenMaxTTL | string | no | Maximum lifetime of issued tokens including renewals, as a duration. Unset or 0 uses the mount or system max TTL. Maps to `token_max_ttl`. Example: 8h | ||
spec.tokenNoDefaultPolicy | boolean | no | When true, the default policy is not attached to issued tokens; only the listed policies apply. Defaults to false. Maps to `token_no_default_policy`. Example: true | ||
spec.tokenNumUses | integer (int32) | no | Maximum number of requests an issued token may make; 0 or unset means unlimited. Maps to `token_num_uses`. Example: 10 | Constraintsvalue: >=0 | |
spec.tokenPeriod | string | no | Makes issued tokens periodic: they never expire as long as they are renewed within this duration, and each renewal resets the TTL to it. Unset or 0 means not periodic. Maps to `token_period`. Example: 1h | ||
spec.tokenPolicies | []string | no | OpenBao policy names attached to issued tokens, in addition to the default policy and the policies from policyRefs. Maps to `token_policies`. Example: [app-read, app-write] | Constraintsitems: <=256list type: set each item: length: >=1, <=128 | |
spec.tokenStrictlyBindIP | boolean | no | When true, issued tokens can only be used from the IP address of the client that logged in. Built-in auth methods only: an external plugin built on an older OpenBao SDK ignores it and never returns it. Defaults to false. Maps to `token_strictly_bind_ip`. Example: true | ||
spec.tokenTTL | string | no | Initial lifetime of issued tokens, as a duration. Unset or 0 uses the mount or system default TTL; must not exceed tokenMaxTTL. Maps to `token_ttl`. Example: 1h | ||
spec.tokenType | string | no | Type of token to issue. One of default (the mount's default, normally service), service (renewable, can create child tokens) or batch (lightweight, not renewable). Maps to `token_type`. Example: service | Constraintsone of:default, service, batch | |
status | object | no | Observed state of the role, written by the operator. | ||
status.acquired | string | no | How the operator came to own the object: Created (it created it) or Adopted (it took over an existing one). Empty until owned. | ||
status.conditions | []object | no | Current state as conditions: Ready (the OpenBao object matches the spec) and Synced (the last reconcile succeeded), each with a reason such as Available, Drifted, Conflict, ConnectionNotReady or PermissionDenied, and the generation it describes. | Constraintslist type: map (keys: type) | |
status.conditions[] | object | no | Condition contains details for one aspect of the current state of this API Resource. | ||
status.conditions[].lastTransitionTime | string (date-time) | yes | lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. | ||
status.conditions[].message | string | yes | message is a human readable message indicating details about the transition. This may be an empty string. | Constraintslength: <=32768 | |
status.conditions[].observedGeneration | integer (int64) | no | observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. | Constraintsvalue: >=0 | |
status.conditions[].reason | string | yes | reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. | Constraintspattern:^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$length: >=1, <=1024 | |
status.conditions[].status | string | yes | status of the condition, one of True, False, Unknown. | Constraintsone of:True, False, Unknown | |
status.conditions[].type | string | yes | type of condition in CamelCase or in foo.example.com/CamelCase. | Constraintspattern:^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$length: <=316 | |
status.id | string | no | Identifier OpenBao generated for the object (an entity, group or alias ID, or a mount accessor), for kinds that have one; other resources reference it. Example: 6c9f3e0a-1b2c-4d5e-8f90-123456789abc | ||
status.namespace | string | no | Absolute OpenBao namespace the object was written in; empty means the root namespace. If it later differs from the spec, reconciling stops with reason NamespaceChanged. Example: team-a/apps | ||
status.observedGeneration | integer (int64) | no | The metadata.generation of this resource that the operator last reconciled. | ||
status.path | string | no | Full OpenBao API path of the object, including its namespace, as last written; deletion uses it even after the spec changed. Example: team-a/sys/policies/acl/app-read | ||
status.rotationNonce | string | no | Value of the resource's rotation nonce when one-time inputs, such as a root credential that OpenBao rotates afterwards, were last sent; changing the nonce in the spec sends them again. | ||
status.serverID | string | no | Cluster ID of the OpenBao server the object was acquired on. If the connection later reaches another server, reconciling stops with reason ServerChanged and nothing is written or deleted. Example: 80f7de92-c12e-e960-4754-255c32fc6b53 | ||
status.writeOnlyHash | string | no | Keyed hash (HMAC-SHA256) of the write-only inputs, such as passwords read from Secrets; a change forces a write. It never contains or reveals the values. |