-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
DNS lookup attempted on externalNames that are IPs, causing errors in the logs #8941
Comments
@sonjalim: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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. |
It seems like it's not checking if it's an IP address and attempting to do a DNS look-up even if it is. From this discussion on the kubernetes forum, it seems like we should expect it to work? |
https://kubernetes.io/docs/concepts/services-networking/service/#externalname ExternalName: Maps the Service to the contents of the externalName field (e.g. foo.bar.example.com), by returning a CNAME record with its value. No proxying of any kind is set up. Also this ;
An IP address in the value for that field can return a /remove-kind bug |
@longwuyuan: Closing this issue. 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. |
* optimize(dkhptd): tuning resource request * refactor(backup): change backup message, reduce backup r2 retention to 7 days * feat(loki): add log retention? * fix(loki): simple scalable require disable other deployment nodes * fix(ingress): fix anoying error of service type: ExternalName kubernetes/ingress-nginx#8941
What happened:
Getting error message for services that use IP in the
spec.externalName
fieldWhat you expected to happen:
Expected these errors do not occur
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use
kubectl version
):Environment:
Cloud provider or hardware configuration: Google Cloud
OS (e.g. from /etc/os-release): linux
Kernel (e.g.
uname -a
): 5.4.188+Install tools: gcloud
How was the ingress-nginx-controller installed:
How to reproduce this issue:
Service and ingress that reproduces the error
The text was updated successfully, but these errors were encountered: