Skip to content

fix(crds): refresh embedded CRDs from butler-api v0.17.0 - #35

Merged
atbagan merged 1 commit into
mainfrom
fix/embedded-crds-from-butler-api-v0.17.0
May 19, 2026
Merged

atbagan merged 1 commit into
mainfrom
fix/embedded-crds-from-butler-api-v0.17.0

Conversation

@atbagan

@atbagan atbagan commented May 19, 2026

Copy link
Copy Markdown
Contributor

No description provided.

The bootstrap controller overlays embedded CRDs from internal/crds/
on top of whatever the butler-crds chart installs, to keep any
binary-side type extensions canonical on tenant clusters. After the
audit bumped butler-api to v0.17.0, the embedded CRDs were not
regenerated. They stayed at the schema shipped before the audit and
overwrote the newer chart CRDs at install time.

Concrete symptom: butler-addons 0.8.4 install fails with
AddonDefinition validation error on spec.category "dns" and unknown
fields spec.iconData / spec.tier. butler-crds chart 0.20.0 has the
correct schema, but the embedded overlay reverts the AddonDefinition
CRD to an older schema before butler-addons attempts to create its
resources.

Copied 6 CRDs verbatim from butler-api v0.17.0 config/crd/bases:
- addondefinitions: adds dns, database, messaging, service-mesh to
  category enum; adds iconData and tier fields
- butlerconfigs: schema additions from v0.13 -> v0.17
- providerconfigs: schema additions
- teams: schema additions (largest delta, +345 lines)
- tenantaddons: schema additions
- tenantclusters: schema additions

The embedded CRDs now match butler-api v0.17.0, which matches the
butler-crds chart 0.20.0 schema. butler-addons 0.8.4 AddonDefinitions
will validate against the live CRD after this lands.

Future butler-api bumps must regenerate these embedded CRDs.
Surfaced as a finding in ~/code/notes/butler-platform-findings.md.
@atbagan
atbagan merged commit 3b8c7f2 into main May 19, 2026
4 checks passed
@atbagan
atbagan deleted the fix/embedded-crds-from-butler-api-v0.17.0 branch May 19, 2026 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant