0.17.0

Cutting the Dead Wood

1. A courageous engineering ritual in which legacy features are gracefully retired to /dev/null.

🚨 Breaking changes

With this release, operators can now configure and manage the namespace used by the Korifi gateway. When upgrading from Korifi 0.16.1, follow one of these approaches:

• To continue using korifi-gateway as the gateway namespace:

  • Before upgrading, add the annotation helm.sh/resource-policy: keep to the namespace to prevent Helm from deleting it (see Helm documentation). Use: kubectl annotate namespace korifi-gateway --overwrite "helm.sh/resource-policy"="keep".
  • During the upgrade, leave the networking.gatewayNamespace Helm value unset.
  • If you missed the annotation before upgrading and the gateway namespace is deleted, recreate it (kubectl create namespace korifi-gateway) and rerun the upgrade with your previous Helm values.

• To switch to a new namespace:

  • Create your desired namespace before upgrading (e.g., kubectl create namespace mygw-namespace).
  • Set the networking.gatewayNamespace Helm value to this namespace (e.g., --set=networking.gatewayNamespace="mygw-namespace") during the upgrade.
  • The upgrade process will automatically remove the old korifi-gateway namespace.

What's Changed

Helm chart

• Chart simplifications:
  • All controllers and webhooks are deployed as a single deployment (korifi-controllers) to simplify the build process and reduce maintenance efforts.
  • The debug helm value has been removed to reduce helm chart complexity.
• Introduce the networking.gatewayNamespace helm value (defaulted to korifi-gateway) to configure the namespace of the Korifi gateway (thanks @vkazmin1).
• Chart templates use Chart.Version to correctly label helm hook jobs (thanks @vkazmin1)

CF API compatibility improvements

• cf CLI users can now create multiple bindings to the same service instance using the --binding-name option with the bind-service command.

Misc Improvements

• The installation guide now includes correct kpack links (thanks @gogolok).
• The deploy-on-kind script always uses the locally installed yq to prevent conflicts with system versions (thanks @gogolok).

Full Changelog: v0.16.1...v0.17.0

⚒️ Ready to try it? Check out the installation instructions!