Skip to content

Secrets engine resources · Kind catalogue · Examples

KubernetesSecretsRole

API version: secrets.openbaoconfig.io/v1alpha1
Scope: Namespaced
Resource: kubernetessecretsroles.secrets.openbaoconfig.io
Categories: openbao

KubernetesSecretsRole manages a role of a Kubernetes secrets engine at `<mount>/roles/<name>`, from which OpenBao issues short-lived Kubernetes service account tokens (`<mount>/creds/<name>`). Use it to hand out scoped cluster access without long-lived tokens.

Example:

spec:
  connectionRef:
    name: openbao
  mountPath: kubernetes
  name: ci-deployer
  allowedKubernetesNamespaces: [apps-dev]
  kubernetesRoleName: edit
  kubernetesRoleType: ClusterRole

Example

examples/secrets/kubernetessecretsrole.yaml
apiVersion: secrets.openbaoconfig.io/v1alpha1
kind: KubernetesSecretsRole
metadata:
  name: obco-app-sa
  namespace: openbao-config
spec:
  connectionRef:
    kind: OpenBaoConnection
    name: openbao
  creationPolicy: CreateOrAdopt
  deletionPolicy: Delete
  driftDetection: Enabled
  mountPath: kubernetes
  name: obco-app-sa
  allowedKubernetesNamespaces:
    - openbao-config
  tokenDefaultTTL: 1h
  tokenMaxTTL: 4h
  tokenDefaultAudiences:
    - https://kubernetes.default.svc
  serviceAccountName: obco-app
  kubernetesRoleType: Role
  nameTemplate: '{{ printf "obco-%s-%s" (.RoleName | truncate 16) (random 8) | lowercase }}'
  extraLabels:
    app.kubernetes.io/managed-by: openbao
  extraAnnotations:
    obco.example/owner: platform
---
apiVersion: secrets.openbaoconfig.io/v1alpha1
kind: KubernetesSecretsRole
metadata:
  name: obco-app-generated
  namespace: openbao-config
spec:
  connectionRef:
    name: openbao
  mountPath: kubernetes
  allowedKubernetesNamespaceSelector: '{"matchLabels":{"obco.example/tenant":"sandbox"}}'
  kubernetesRoleType: ClusterRole
  generatedRoleRules: |
    rules:
      - apiGroups: [""]
        resources: ["pods"]
        verbs: ["get", "list"]
---
apiVersion: secrets.openbaoconfig.io/v1alpha1
kind: KubernetesSecretsRole
metadata:
  name: obco-app-bound
  namespace: openbao-config
spec:
  connectionRef:
    name: openbao
  mountPath: kubernetes
  allowedKubernetesNamespaces:
    - openbao-config
  kubernetesRoleName: obco-app-reader

On GitHub: kubernetessecretsrole.yaml, generated sample with every field.

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.

FieldTypeRequiredDefaultDescriptionValidation
specobjectyesspec is the desired role of a Kubernetes secrets engine at `<mountPath>/roles/<name>`. A role issues a token for an existing service account (serviceAccountName), binds a generated service account to an existing Role or ClusterRole (kubernetesRoleName), or generates the whole chain (generatedRoleRules); set exactly one.
ConstraintsCEL: 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.allowedKubernetesNamespaces) || has(self.allowedKubernetesNamespaceSelector) (set allowedKubernetesNamespaces or allowedKubernetesNamespaceSelector)
CEL: [has(self.serviceAccountName), has(self.kubernetesRoleName), has(self.generatedRoleRules)].filter(x, x).size() == 1 (set exactly one of serviceAccountName, kubernetesRoleName and generatedRoleRules)
CEL: !has(self.tokenDefaultTTL) || !has(self.tokenMaxTTL) || duration(self.tokenMaxTTL) == duration('0s') || duration(self.tokenDefaultTTL) <= duration(self.tokenMaxTTL) (tokenDefaultTTL 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.allowedKubernetesNamespaceSelectorstringnoallowedKubernetesNamespaceSelector is a label selector, as JSON or YAML, for the namespaces credentials may be generated in (`allowed_kubernetes_namespace_selector`). With allowedKubernetesNamespaces both conditions must hold. Example: `{"matchLabels": {"team": "billing"}}`.
Constraintslength: <=8192
spec.allowedKubernetesNamespaces[]stringnoallowedKubernetesNamespaces lists the namespaces credentials may be generated in (`allowed_kubernetes_namespaces`); `*` allows all. Set this or allowedKubernetesNamespaceSelector. Up to 256. Example: `[apps-dev]`.
Constraintsitems: <=256
list type: set
each item: length: <=63
spec.connectionRefobjectyesConnection used to reach and log in to OpenBao. Immutable.
spec.connectionRef.kindstringno"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.namestringyesName of the OpenBaoConnection or ClusterOpenBaoConnection. Example: openbao
Constraintslength: >=1, <=253
spec.creationPolicystringno"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.deletionPolicystringno"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.driftDetectionstringno"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.driftIntervalstringnoHow 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: <=32
CEL: duration(self) >= duration('30s') (driftInterval must be at least 30s)
spec.extraAnnotationsmap[string]stringnoextraAnnotations are added to every generated object (`extra_annotations`). Up to 64. Example: `{owner: billing}`.
Constraintsproperties: <=64
spec.extraLabelsmap[string]stringnoextraLabels are added to every generated object (`extra_labels`). Up to 64. Example: `{managed-by: openbao}`.
Constraintsproperties: <=64
spec.generatedRoleRulesstringnogeneratedRoleRules are the rules, as JSON or YAML, of the Role or ClusterRole that OpenBao generates (`generated_role_rules`). Example: `{"rules": [{"apiGroups": [""], "resources": ["pods"], "verbs": ["list"]}]}`.
Constraintslength: <=65536
spec.kubernetesRoleNamestringnokubernetesRoleName is an existing Role or ClusterRole that generated service accounts are bound to (`kubernetes_role_name`). Example: `edit`.
Constraintslength: <=253
spec.kubernetesRoleTypestringnokubernetesRoleType is the kind of the referenced or generated role (`kubernetes_role_type`). Allowed: Role, ClusterRole. Defaults to Role.
Constraintsone of: Role, ClusterRole
spec.managementPolicystringno"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.mountPathstringyesmountPath is the path of the Kubernetes secrets engine mount, without leading or trailing slashes. Immutable. Example: `kubernetes`.
Constraintspattern: ^[A-Za-z0-9_.-]+(/[A-Za-z0-9_.-]+)*$
length: >=1, <=128
spec.namestringnoname is the role name in OpenBao, lower case. Defaults to metadata.name. Immutable. Example: `ci-deployer`.
Constraintspattern: ^[a-z0-9_]([a-z0-9_.-]*[a-z0-9_])?$
length: >=1, <=128
spec.nameTemplatestringnonameTemplate is the template for the names of generated objects (`name_template`). Example: `{{.RoleName}}-{{random 8}}`.
Constraintslength: <=1024
spec.namespacestringnoOpenBao 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.serviceAccountNamestringnoserviceAccountName is an existing service account to generate tokens for (`service_account_name`). Example: `deployer`.
Constraintslength: <=253
spec.tokenDefaultAudiences[]stringnotokenDefaultAudiences are the default audiences of generated tokens (`token_default_audiences`). Empty uses the cluster's default audience. Up to 32. Example: `[https://kubernetes.default.svc]`.
Constraintsitems: <=32
list type: set
each item: length: <=256
spec.tokenDefaultTTLstringnotokenDefaultTTL is the default lifetime of generated tokens (`token_default_ttl`), a duration. Must not exceed tokenMaxTTL. Defaults to the mount's default lease TTL. Example: `1h`.
Constraintspattern: ^(0|([0-9]+(\.[0-9]+)?(ns|us|ms|s|m|h))+)$
spec.tokenMaxTTLstringnotokenMaxTTL is the maximum lifetime of generated tokens (`token_max_ttl`), a duration. Defaults to the mount's max lease TTL. Example: `24h`.
Constraintspattern: ^(0|([0-9]+(\.[0-9]+)?(ns|us|ms|s|m|h))+)$
statusobjectnostatus is the observed state of the Kubernetes secrets role.
status.acquiredstringnoHow the operator came to own the object: Created (it created it) or Adopted (it took over an existing one). Empty until owned.
status.conditions[]objectnoCurrent 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[]objectnoCondition contains details for one aspect of the current state of this API Resource.
status.conditions[].lastTransitionTimestring (date-time)yeslastTransitionTime 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[].messagestringyesmessage is a human readable message indicating details about the transition. This may be an empty string.
Constraintslength: <=32768
status.conditions[].observedGenerationinteger (int64)noobservedGeneration 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[].reasonstringyesreason 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[].statusstringyesstatus of the condition, one of True, False, Unknown.
Constraintsone of: True, False, Unknown
status.conditions[].typestringyestype 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.idstringnoIdentifier 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.namespacestringnoAbsolute 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.observedGenerationinteger (int64)noThe metadata.generation of this resource that the operator last reconciled.
status.pathstringnoFull 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.rotationNoncestringnoValue 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.serverIDstringnoCluster 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.writeOnlyHashstringnoKeyed 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.