k8gb v0.20.0 is a feature release introducing a cluster-scoped ZoneDelegation CRD for dynamic DNS zone lifecycle management and adding TLSRoute support. The release removes the dynamicZones configuration field and changes ZoneDelegation naming conventions; operators must migrate existing configurations. Multiple reliability fixes improve health checking, DNS validation, and reconciliation behavior.
breakingdynamicZones config field removed; migrate to ZoneDelegation CRD
The dynamicZones configuration field has been removed from values.yaml in v0.20.0. Operators currently using dynamicZones must migrate to the new cluster-scoped ZoneDelegation CRD for declarative DNS zone activation and retirement.
breakingCreateZoneDelegation renamed to SaveZoneDelegation
The ZoneDelegation CRD internal method CreateZoneDelegation has been renamed to SaveZoneDelegation in v0.20.0. This affects integrations or tooling that directly reference the old name.
breakingZoneDelegation names no longer include .conf suffix
ZoneDelegation names no longer include the .conf suffix in v0.20.0. Existing manifests using the old naming convention must be updated.
Key changes (7)
- New cluster-scoped ZoneDelegation CRD enables teams to declaratively activate and retire DNS zones
- TLSRoute support added across multiple gateway.networking.k8s.io API versions
- dynamicZones config field removed; migration to ZoneDelegation CRD required
- Server health check now requires all services to be healthy (previously a subset)
- CreateZoneDelegation method renamed to SaveZoneDelegation; ZoneDelegation naming changed to drop .conf suffix
- Fixes include invalid localtargets DNS label validation, wrong INFOBLOX_WAPI_PORT default, legacy GSLB annotation preservation, and reliability improvements in ZoneDelegation reconciliation and migration cleanup
- Added k8gb.io/exposed-hostnames annotation