K8SPSMDB-1608: add externaldns annotation to create dns for created loadbalancer#2280
Merged
hors merged 21 commits intoJun 11, 2026
Merged
Conversation
myJamong
requested review from
egegunes,
gkech,
hors,
mayankshah1607,
nmarukovich,
oksana-grishchenko and
pooknull
as code owners
myJamong
changed the title
egegunes
changed the title
egegunes
requested changes
Mar 10, 2026
Comment on lines
+1466
to
+1467
| // +kubebuilder:validation:Required | ||
| Prefix string `json:"prefix"` |
Contributor
There was a problem hiding this comment.
maybe prefix shouldn't be required and operator should use the cluster name by default
Contributor
Author
There was a problem hiding this comment.
I think its a great idea. I changed it to have default cr name - ee194e4
Comment on lines
+36
to
+38
| if dns.Prefix == "" || dns.Domain == "" { | ||
| return errors.Errorf("externalDNS requires both prefix and domain for replset %s", rs.Name) | ||
| } |
Contributor
There was a problem hiding this comment.
even though this will be handled on CRD level, I think we should do this check in CheckNSetDefaults
Contributor
Author
There was a problem hiding this comment.
I moved the validation logic - 19a85b2
Thanks for the review!
…unctions to CheckNSetDefaults.
egegunes
previously approved these changes
Mar 10, 2026
Contributor
|
@myJamong please fix manifests by running |
myJamong
requested review from
eleo007,
jvpasinatto and
valmiranogueira
as code owners
egegunes
previously approved these changes
Mar 11, 2026
hors
previously approved these changes
Apr 12, 2026
pooknull
previously approved these changes
Apr 14, 2026
hors
previously approved these changes
May 15, 2026
gkech
changed the title
gkech
previously approved these changes
May 25, 2026
mayankshah1607
previously approved these changes
May 26, 2026
Co-authored-by: Mayank Shah <mayankshah1614@gmail.com>
myJamong
dismissed stale reviews from egegunes, gkech, mayankshah1607, and hors
via
3112f13
Member
|
@myJamong you'll need to run |
Contributor
|
@myJamong please check the failing unit tests |
Co-authored-by: Mayank Shah <mayankshah1614@gmail.com>
egegunes
approved these changes
Jun 10, 2026
Collaborator
commit: 43b99c0 |
mayankshah1607
approved these changes
Jun 11, 2026
Collaborator
|
@myJamong thanks for your contribution! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CHANGE DESCRIPTION
Problem:
When
expose.enabled: truewithtype: LoadBalancer, each per-pod Service gets an auto-assigned LB hostname (e.g.,a1b2c3d4e5.elb.amazonaws.com). These hostnames are not human-readable, long, and unpredictable. The existingexpose.annotationsfield applies the same annotations to every per-pod Service, making it impossible to assign a uniqueexternal-dns.alpha.kubernetes.io/hostnameper pod.This is the issue I made: #2267
Cause:
There was no built-in mechanism to generate unique, per-pod DNS hostname annotations. Users had to manually manage DNS records for each pod's LoadBalancer endpoint.
Solution:
Add an optional
externalDNSfield underexposethat automatically generates uniqueexternal-dns.alpha.kubernetes.io/hostnameannotations for each per-pod Service, enabling ExternalDNS to create human-readable DNS records in any supported DNS provider (Route53, Cloud DNS, Azure DNS, etc.).Configuration
Generated Annotations
Each per-pod Service gets a unique hostname annotation:
my-cluster-rs0-0external-dns.alpha.kubernetes.io/hostname: service-name-rs0-0.mongo.example.commy-cluster-rs0-1external-dns.alpha.kubernetes.io/hostname: service-name-rs0-1.mongo.example.commy-cluster-rs0-2external-dns.alpha.kubernetes.io/hostname: service-name-rs0-2.mongo.example.comIf
ttlis set, theexternal-dns.alpha.kubernetes.io/ttlannotation is also added.Supported Components
{prefix}-{replsetName}-{podIndex}.{domain}{prefix}-mongos-{podIndex}.{domain}{prefix}-mongos.{domain}Note on
serviceAnnotationsoverlapIf
serviceAnnotationscontainsexternal-dns.alpha.kubernetes.io/hostname, theexternalDNSconfig takes precedence and overwrites it. This is by design — whenexternalDNSis configured, it owns the hostname annotation.CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
compare/*-oc.yml)?Config/Logging/Testability