toolhive-operator-crds-0.0.80

A Helm chart for installing the ToolHive Operator CRDs into Kubernetes.

⚠️ Breaking Change: CRD Management Overhaul

This release fundamentally changes how CRDs are managed in the chart.

Background

Helm does not upgrade CRDs placed in the crds/ directory during helm upgrade operations. This is a known issue where CRDs are only processed during initial installation. Subsequent upgrades silently leave CRDs unchanged, even when the chart contains updates. This has resulted in users running with stale CRDs without any indication.

What's Changed

CRDs have been moved from crds/ to templates/ with Helm conditionals. This ensures CRDs are upgraded alongside the chart during helm upgrade, following the pattern used by other popular projects.

Impact

When you upgrade to this release, all CRD changes since your initial installation will be applied. If you have been running an older version, your CRDs may be significantly out of date and this upgrade will bring them current. Please check our examples for more recent examples of the resources.

New Features

• Feature flags: Selectively install CRD groups via crds.install.server, crds.install.registry, and crds.install.virtualMcp
• Keep annotation: CRDs are annotated with helm.sh/resource-policy: keep by default to prevent accidental deletion on uninstall (controlled by crds.keep)

For more details, see the https://github.com/stacklok/toolhive/tree/main/deploy/charts/operator-crds#why-crds-in-templates.

What's Changed

• enable CRD upgrades via Helm with feature flags by @ChrisJBurns in #2809

Full Changelog: toolhive-operator-crds-0.0.79...toolhive-operator-crds-0.0.80