stacklok / toolhive / 25868544070

66%

Build Type

push

github

Committed by web-flow

Commit Message

Drop per-component CRD and controller gating from operator install (#5281)

* Use external helm-crd-wrapper for operator CRD chart

Replace the in-repo crd-helm-wrapper Go program with the external
stacklok/helm-crd-wrapper binary. The external tool intentionally
does not support per-CRD feature gating, so the chart now exposes a
single crds.install boolean instead of per-component flags
(crds.install.server / .registry / .virtualMcp).

Pinned to commit a736420b — no tagged release exists yet; swap for a
tag when one is cut.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Remove controller feature flag gating from operator

The ENABLE_SERVER / ENABLE_REGISTRY / ENABLE_VMCP env vars added in
#3093 let chart consumers selectively start controller groups. We
have no remaining use case for partial controller installs — the
chart now ships all CRDs together, and the operator should match.

- Drop feature flag constants, dependency map, and isFeatureEnabled
  helper from main.go; setupControllersAndWebhooks now calls each
  setup helper unconditionally.
- Delete main_test.go (only tested the removed helper).
- Drop operator.features.{server,registry,virtualMCP} from
  values.yaml and the corresponding ENABLE_* env vars from the
  Deployment template.
- Regenerate operator chart README via helm-docs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Coverage Stats

0 of 6 new or added lines in 1 file covered. (0.0%)

23 existing lines in 5 files now uncovered.

64693 of 98744 relevant lines covered (65.52%)

60.52 hits per line