Breaking Changes
In this release, we updated our Gateway API dependency to v1.1.0. The update from v1.0.0 should be relatively painless, unless you are using the BackendTLSPolicy
resource. If you are using the BackendTLSPolicy
resource, the easiest way to update is to delete all your existing BackendTLSPolicies, update the CRDs and Caddy Gateway, then re-create your resources using the newer v1alpha3
version.
Update commands:
# Install Gateway API CRDs (including those that are experimental)
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.1.0/experimental-install.yaml
# Install Gateway API CRDs (only stable resources)
# NOTE: **Do not use this command if you already ran the `experimental-install`**
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.1.0/standard-install.yaml
See https://gateway-api.sigs.k8s.io/guides/#v11-upgrade-notes for more details on upgrading.
Changelog
Added
- 3b5baa1: feat: add support for
TCPRoute
,TLSRoute
, andUDPRoute
(#4) (@matthewpi) - e4859c2: feat: add support for
kubernetes.io/h2c
app protocol (@matthewpi)
Fixed
- 048a7c6: fix(controller): remove debug log that leaks the entire caddy config (@matthewpi)
Documentation
- 384a56d: docs: update caddy example to use 2.8.0 (@matthewpi)
CI
- 7ab0208: build(goreleaser): tweak release footer (@matthewpi)
- 96551ae: ci: add
caddy
image build workflow (@matthewpi)
Other work
- d4dcc95: chore!: upgrade to Gateway API v1.1.0 (#3) (@matthewpi)
- d8d38ba: nix: update flake.lock (@matthewpi)
Full Changelog: v0.0.1...v0.1.0