zeekayandHanzo Dev 8894a6712c Let one binary serve any universe's KMS group ...

The group moved to kms.hanzo.ai/v1 here already, which is the right name — but
it is still a compile-time constant, so this binary can serve a Hanzo install
and no other. A Lux cluster needs kms.lux.cloud and there is no way to ask for
it short of a rebuild.

SetGroup makes it an argument behind --api-group, defaulting to kms.hanzo.ai,
the way hanzoai/operator and luxfi/operator already take theirs.

Registration moves out of init and into main, after the flag is read. The
SchemeBuilder captures its GroupVersion when the types register, so registering
first and setting the group afterwards leaves the scheme on one group while the
manager watches another. That controller starts clean, logs nothing, and never
sees an object — it reads as "no work to do" rather than as a misconfiguration,
so the ordering is asserted in a test rather than left to whoever edits main
next.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-01 08:06:56 -07:00

..

v1

Let one binary serve any universe's KMS group

2026-09-01 08:06:56 -07:00