AuthentikBrand
Mirrors authentik_brand.
- API version:
authentik.weebo.io/v1alpha1 - Scope: Cluster
- Short names: none
Mirrors authentik_brand. Cluster-scoped — a brand is tied to a domain
at the instance level, not to an application namespace. See
.prompt/plan.md, "Election du brand par defaut" for the default
field's reconcile semantics (implemented in domain::brand_election,
wired up in the application crate's reconcile_brand use-case).
Example
apiVersion: authentik.weebo.io/v1alpha1
kind: AuthentikBrand
metadata:
name: my-brand
spec:
domain: login.example.com
brandingTitle: Weebo
default: true
flowAuthentication: default-authentication-flowSpec fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
brandingDefaultFlowBackground | string | no | ||
brandingFavicon | string | no | ||
brandingLogo | string | no | ||
brandingTitle | string | no | ||
default | boolean | no | false | |
defaultApplicationRef | string | no | Name of an AuthentikApplication CR, same-namespace convention does not apply here since this CRD is cluster-scoped. | |
domain | string | yes | ||
flowAuthentication | string | no | Flow slugs, resolved at reconcile time. These reference a flow by slug whether or not an AuthentikFlow CR manages it — the reference is always slug-based, never a Kubernetes CR lookup. | |
flowInvalidation | string | no | ||
flowRecovery | string | no | ||
flowUnenrollment | string | no | ||
flowUserSettings | string | no |
Build a manifest
Answer the questions and fill in the fields: the YAML preview updates as you type, ready to copy or download and kubectl apply.
Loading form...