Repository navigation
feat(service): publish externalIPs for ClusterIP services - #6951
mloiseleur wants to merge 2 commits into
Conversation
A non-headless ClusterIP Service with spec.externalIPs produced no targets unless --publish-internal-services or the internal-hostname annotation was set. Use the externalIPs in that case, as LoadBalancer and ExternalName Services already do. The ClusterIP still wins when --publish-internal-services or the internal-hostname annotation is set, so existing records do not change.
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Coverage Report for CI Build 43067938124Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage increased (+0.004%) to 83.475%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions28 previously-covered lines in 2 files lost coverage.
Coverage Stats
💛 - Coveralls |
What does it do ?
A non-headless ClusterIP Service now publishes its
spec.externalIPs, as LoadBalancer and ExternalName Services already do.--publish-internal-servicesand theinternal-hostnameannotation still use the ClusterIP, so existing records do not change.New records appear for ClusterIP Services that have
spec.externalIPsand a hostname annotation or a matching--fqdn-template.Motivation
Fixes #1281
More