-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NodePort SRV
combine different ports producing issues in client libs
#4000
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened:
Using industry starand bitnami mongodb-sharded chart to create a database that we'll expose using srv records. The chart will create a service along the lines of:
The SRV records created by
external-dns
will merge both ports causing an error preventing the client to establish a connectionAlso, SRV services name are well-defined for each client, and in the case of mongodb the client expects the following pattern:
_mongodb._tcp.{{host}}
. This will only be achievable by farcing the name of the service to bemongodb
which attempts against best practices. Service's names are expected to be self explanatory and not abstract protocolsWhat you expected to happen:
It will be much better to get the fqdn using the port's name to construct the following 2 records:
How to reproduce it (as minimally and precisely as possible):
Just create a basic service of type
NodePort
and expose 2 different ports. Any service that follows this pattern will workAnything else we need to know?:
Environment:
external-dns --version
):v0.13.6
aws
6.26.5
The text was updated successfully, but these errors were encountered: