Expand description
White-labeled naming for the access-request custom resource.
The operator manifest (alien-helm) and the operator runtime
(alien-access-request-crd-loop) BOTH derive the CRD’s group/kind/plural
from the deployment’s brand name here, so the resource the manifest
registers is exactly the one the operator creates and watches — they can’t
drift.
Kubernetes requires the API group to be shaped like a DNS subdomain, but never resolves it — so the brand isn’t a domain the vendor owns, just a stable, customer-facing identity (e.g. the project name) slugified into that shape.
For a vendor branded acme, the access-request CRD is:
group: accessrequests.acme
kind: AcmeAccessRequest
plural: acmeaccessrequests
short: acmearWhen no brand is set it falls back to the Alien defaults
(accessrequests.alien / AlienAccessRequest).
Structs§
- Access
Request CrdNames - Derived, white-labeled names for the access-request custom resource.
Constants§
- ACCESS_
REQUEST_ CRD_ VERSION - The CRD version served (single alpha version for now).
- DEFAULT_
BRAND - The default (unbranded) slug the access-request CRD lives under.
Functions§
- access_
request_ crd_ names - Derive the access-request-CRD names from a brand name (e.g.
Some("acme"), orSome("Acme Corp")).None/empty → the Alien defaults. - brand_
slug - The lowercase alphanumeric brand slug from a name’s first dot-separated label (so a real domain’s first label still works as input), with any remaining non-alphanumerics (spaces, punctuation) stripped out.
- current_
kubernetes_ label_ domain - Returns the DNS-safe label domain used by current Kubernetes resources.
- explicit_
legacy_ kubernetes_ label_ domain - Returns a valid, distinct legacy label domain for a branded deployment.
- is_
valid_ kubernetes_ label_ domain - Whether a value can safely serve as the domain portion of a Kubernetes label key.