You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting "default-backend" annotation on an ingress to a service which points to an externalName, the ingress won't updated. If editing again, the annotation is gone. If i set it to a ClusterIP service, it works fine.
When setting the default-backend to my externalname service, the controller logs the following
Would think the externalName service could be used as a default-backend for an Ingress
Does it seem the service you are creating has no ports defined? Please make sure you have one (without it, the ingress controller does not know where to send the traffic)
NGINX Ingress controller version:
0.33
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-21T14:51:23Z", GoVersion:"go1.14.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.6-beta.0", GitCommit:"e7f962ba86f4ce7033828210ca3556393c377bcc", GitTreeState:"clean", BuildDate:"2020-01-15T08:18:29Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}
Environment:
Docker-For-Mac
What happened:
When setting "default-backend" annotation on an ingress to a service which points to an externalName, the ingress won't updated. If editing again, the annotation is gone. If i set it to a ClusterIP service, it works fine.
When setting the default-backend to my externalname service, the controller logs the following
What you expected to happen:
Would think the externalName service could be used as a default-backend for an Ingress
/kind bug
The text was updated successfully, but these errors were encountered: