api, charts, config, internal, docs: every API group is under nats-operator.io #20

Merged

mikluko merged 1 commit from mikluko/api-domain-nats-operator-io into main

2026-10-04 13:22:02 +00:00

mikluko commented

2026-10-04 13:05:21 +00:00

(Migrated from github.com)

nats.mikluko.io becomes nats-operator.io, with any subgroup prefix or path suffix: the four API groups, finalizers, annotations, labels, the JetStream ownership metadata keys, field indexes, Lease names and CRD names. Versions and kinds stay. The released sections of CHANGELOG.md keep the old domain.

Not a plain substitution:

The CRD files are renamed, as their names hold the group. Regenerating (just verify) gives byte for byte what the substitution gave.
The release-name limits stay at 37 and 34 characters. They come from the Service names <release>-jetstream-controller-test and -metrics, which do not hold the domain. A Lease name is one character longer and has no limit that a release name can reach.
CHANGELOG.md has the breaking entry, and the install page has "Upgrade from 0.2.x or earlier".

Upgrade: there is no migration. The page says to remove the old version with everything it deployed (the Uninstall steps), then delete the servers' PersistentVolumeClaims and the generated seed Secrets, install the new version and apply the manifests under the new groups. The two extra deletions are there because a NatsCluster of the same name mounts a claim that remains, and the auth controller refuses a generated seed Secret that lacks auth.nats-operator.io/generated-for.

Not verified: the upgrade steps were not run against a 0.2.0 install. e2e ran stories 1 and 2 only, on recreated kind clusters; on the standing clusters the run hung in "fresh namespace", on an old-group NatsCluster whose finalizer no controller removes.

`nats.mikluko.io` becomes `nats-operator.io`, with any subgroup prefix or path suffix: the four API groups, finalizers, annotations, labels, the JetStream ownership metadata keys, field indexes, Lease names and CRD names. Versions and kinds stay. The released sections of `CHANGELOG.md` keep the old domain. Not a plain substitution: - The CRD files are renamed, as their names hold the group. Regenerating (`just verify`) gives byte for byte what the substitution gave. - The release-name limits stay at 37 and 34 characters. They come from the Service names `<release>-jetstream-controller-test` and `-metrics`, which do not hold the domain. A Lease name is one character longer and has no limit that a release name can reach. - `CHANGELOG.md` has the breaking entry, and the install page has "Upgrade from 0.2.x or earlier". Upgrade: there is no migration. The page says to remove the old version with everything it deployed (the Uninstall steps), then delete the servers' PersistentVolumeClaims and the generated seed Secrets, install the new version and apply the manifests under the new groups. The two extra deletions are there because a `NatsCluster` of the same name mounts a claim that remains, and the auth controller refuses a generated seed Secret that lacks `auth.nats-operator.io/generated-for`. Not verified: the upgrade steps were not run against a 0.2.0 install. e2e ran stories 1 and 2 only, on recreated kind clusters; on the standing clusters the run hung in "fresh namespace", on an old-group `NatsCluster` whose finalizer no controller removes.