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
kubectl cluster-info
Kubernetes control plane is running at https://31.172.*.*
CoreDNS is running at https://31.172.*.*/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
KubeDNSUpstream is running at https://31.172.*.*/api/v1/namespaces/kube-system/services/kube-dns-upstream:dns/proxy
6. What did you expect to happen?
As the api spec looks like:
I expect kops to not allocate a floating ip for the api loadbalancer. Also kops should configure kubernetes to use the internal loadbalancer IP as API endpoint.
8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.
I will provide this if it is useful for troubleshooting. Because it will take some time to redact the massive amount of log outputs.
The text was updated successfully, but these errors were encountered:
I did some more research and it seems kind of work when using public DNS - but then kops does not set the DNS records, I have to set it manually:
topology:
dns:
type: Public
The problem ist that the DNS record for api.internal. is never created. If I create it by hand then all nodes join the cluster.
So am I missing some essential config node or is it a bug?
/kind bug
1. What
kops
version are you running?2. What Kubernetes version are you running?
3. What cloud provider are you using?
Openstack
4. What commands did you run? What is the simplest way to reproduce this issue?
5. What happened after the commands executed?
6. What did you expect to happen?
As the api spec looks like:
I expect kops to not allocate a floating ip for the api loadbalancer. Also kops should configure kubernetes to use the internal loadbalancer IP as API endpoint.
7. Please provide your cluster manifest.
8. Please run the commands with most verbose logging by adding the
-v 10
flag.Paste the logs into this report, or in a gist and provide the gist link here.
I will provide this if it is useful for troubleshooting. Because it will take some time to redact the massive amount of log outputs.
The text was updated successfully, but these errors were encountered: