-
Notifications
You must be signed in to change notification settings - Fork 292
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
External IP Address Missing from AKS Service Spec #176
Comments
@nickward13 Any chance you can send the bare YAML? My guess is there is a parse error somewhere in the c# code... Thanks! |
Thanks again @brendanburns. Will do. |
Ok - I think I've got to the bottom of it. The external IP is correctly returned by the KubernetesClient in Status.LoadBalancer.Ingress[].Ip, not where I was initially looking for it in Spec.ExternalIps, which is still null. I'm not sure what is supposed to be in Spec.ExternalIps, however it doesn't seem to list the external IP addresses that are in Status.LoadBalancer.Ingress[]. I had to reproduce the error, as I no longer had the original AKS cluster I was connecting to. Attached is the yaml for the service as received from kubectl, showing the external IP address on the Status.LoadBalancer property. |
Ok, so that is by design.
In general, in Kubernetes I'm going to close this as I think it is working as intended. |
I'm using the library to retrieve the services I have deployed to my AKS cluster. I can successfully retrieve the service I'm after, however the ExternalIPs for the service in question are returned as null, whereas they have an external IP as shown by the kubectl output.
See attached ServiceSpec.png for the spec as received via the client library versus ServiceKubectl.png for the service details as seen from kubectl.
I'm trying to retrieve the "LoadBalancer Ingress" IP address for the service as provided by kubectl, and expected to find it in the ExternalIPs dictionary on the service object returned by the client library. Is it stored somewhere else?
The text was updated successfully, but these errors were encountered: