Skip to content

v0.0.22

  • v0.0.22
  • 908b5e5

  • Partially verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.

  • Choose a tag to compare

    View all tags
v0.0.22: feat: add --cluster-domain flag for custom cluster domains (#264)
  • v0.0.22
  • 908b5e5

  • Choose a tag to compare

    View all tags

  • Partially verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
@robbeverhelst robbeverhelst tagged this 12 Feb 04:47 
* feat: add --cluster-domain flag for custom cluster domains

Kubernetes clusters can use a custom domain via --cluster-domain
(kubelet) instead of the default cluster.local. The controller
hardcoded cluster.local when constructing backend service FQDNs,
causing DNS resolution failures on clusters with custom domains.

Add a --cluster-domain flag (default: cluster.local) and expose
it as a Helm value (clusterDomain).

Fixes #263

* test: use custom cluster domain in tests to verify --cluster-domain flag

Use non-default cluster domains across unit, integration, and e2e tests
to ensure the clusterDomain parameter is actually propagated rather than
relying on the default "cluster.local". Also enrich descriptions for the
--cluster-domain flag and the Helm clusterDomain value.

---------

Co-authored-by: Zhiqiang ZHOU <im@strrl.dev>
Assets 2
Loading