Identity resources · Kind catalogue · Examples
OIDCAssignment¶
API version: identity.openbaoconfig.io/v1alpha1
Scope: Namespaced
Resource: oidcassignments.identity.openbaoconfig.io
Categories: openbao
OIDCAssignment manages an assignment of the OpenBao OIDC provider at `identity/oidc/assignment/<name>`: the entities and groups allowed to log in to the OIDCClient objects that list it in assignments.
Example:
Example:
spec:
connectionRef:
name: openbao
name: billing-users
groups:
- groupRef: {name: billing-admins}Example¶
examples/identity/oidcassignment.yaml
apiVersion: identity.openbaoconfig.io/v1alpha1
kind: OIDCAssignment
metadata:
name: obco-portal-users
namespace: openbao-config
spec:
connectionRef:
kind: OpenBaoConnection
name: openbao
creationPolicy: CreateOrAdopt
driftDetection: Enabled
driftInterval: 30m
managementPolicy: Manage
deletionPolicy: Delete
name: obco-portal-users
entities:
- entityID: 6f1e3c2a-0000-4000-8000-000000000001
- entityName: obco-alice
- entityRef:
name: obco-bob
- entitySelector:
matchLabels:
obco.example.com/portal: "true"
groups:
- groupID: 6f1e3c2a-0000-4000-8000-000000000002
- groupName: obco-developers
- groupRef:
name: obco-operators
- groupSelector:
matchLabels:
obco.example.com/portal: "true"
On GitHub: oidcassignment.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.
| Field | Type | Required | Default | Description | Validation |
|---|---|---|---|---|---|
spec | object | yes | spec is the desired OIDC assignment at `identity/oidc/assignment/<name>`: the entities and groups allowed to authenticate through the OIDC clients that cite it. The lists are written as a whole; members removed from the spec are removed in OpenBao. | ConstraintsCEL:has(self.name) == has(oldSelf.name) && (!has(self.name) || self.name == oldSelf.name) (name is immutable)CEL: !has(self.name) || self.name != 'allow_all' (the assignment allow_all is built in and cannot be changed)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.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.entities | []object | no | entities are the entities in the assignment (`entity_ids`). Up to 256. Example: `[{entityRef: {name: alice}}]`. | Constraintsitems: <=256list type: atomic | |
spec.entities[] | object | no | Selects OpenBao entities by exactly one of an ID, an OpenBao name, an Entity object or a label selector over Entity objects. | ConstraintsCEL:[has(self.entityID), has(self.entityName), has(self.entityRef), has(self.entitySelector)].filter(x, x).size() == 1 (set exactly one of entityID, entityName, entityRef and entitySelector) | |
spec.entities[].entityID | string | no | entityID is the OpenBao ID of an entity. Example: `0b1c6a2e-5d1f-4a7e-9b2e-3c4d5e6f7a8b`. | Constraintslength: <=128 | |
spec.entities[].entityName | string | no | entityName is the OpenBao name of an entity, resolved to its ID through the connection. Example: `alice`. | Constraintslength: <=128 | |
spec.entities[].entityRef | object | no | entityRef names an Entity in the same namespace; it must be Ready. Example: `{name: alice}`. | ||
spec.entities[].entityRef.name | string | yes | Name of the referenced object, in the same namespace as this resource. Example: my-app | Constraintslength: >=1, <=253 | |
spec.entities[].entitySelector | object | no | entitySelector selects every Entity in the same namespace that carries these labels. | ||
spec.entities[].entitySelector.matchLabels | map[string]string | yes | Labels an object must carry, all of them, to be selected. Example: {team: payments} | Constraintsproperties: >=1, <=16CEL: self.all(k, size(k) <= 317 && size(self[k]) <= 63) (label keys must be at most 317 and values at most 63 characters) | |
spec.groups | []object | no | groups are identity groups in the assignment; their member entities are included (`group_ids`). Up to 256. Example: `[{groupName: billing-admins}]`. | Constraintsitems: <=256list type: atomic | |
spec.groups[] | object | no | Selects OpenBao identity groups by exactly one of an ID, an OpenBao name, a Group object or a label selector over Group objects. | ConstraintsCEL:[has(self.groupID), has(self.groupName), has(self.groupRef), has(self.groupSelector)].filter(x, x).size() == 1 (set exactly one of groupID, groupName, groupRef and groupSelector) | |
spec.groups[].groupID | string | no | groupID is the OpenBao ID of a group. Example: `5f1c2d3e-4a5b-6c7d-8e9f-0a1b2c3d4e5f`. | Constraintslength: <=128 | |
spec.groups[].groupName | string | no | groupName is the OpenBao name of a group, resolved to its ID through the connection. Example: `billing-admins`. | Constraintslength: <=128 | |
spec.groups[].groupRef | object | no | groupRef names a Group in the same namespace; it must be Ready. Example: `{name: billing-admins}`. | ||
spec.groups[].groupRef.name | string | yes | Name of the referenced object, in the same namespace as this resource. Example: my-app | Constraintslength: >=1, <=253 | |
spec.groups[].groupSelector | object | no | groupSelector selects every Group in the same namespace that carries these labels. | ||
spec.groups[].groupSelector.matchLabels | map[string]string | yes | Labels an object must carry, all of them, to be selected. Example: {team: payments} | Constraintsproperties: >=1, <=16CEL: self.all(k, size(k) <= 317 && size(self[k]) <= 63) (label keys must be at most 317 and values at most 63 characters) | |
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.name | string | no | name is the assignment name in OpenBao. Defaults to metadata.name. Letters, digits, `_`, `.`, `@` and `-`; `allow_all` is built in and cannot be managed. Immutable. Example: `billing-users`. | Constraintspattern:^\w([\w.@-]*\w)?$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 | |
status | object | no | status is the observed state of the OIDC assignment. | ||
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. |