"DNS is enabled" is printed prematurely
See original GitHub issueWhen I run microk8s enable dns
I see the following output:
Enabling DNS
# ...
DNS is enabled
However this is false:
$ microk8s.kubectl wait --for=condition=ready pod -l k8s-app=kube-dns -n kube-system --timeout=180s
error: no matching resources found
A while later when I repeat the same command
$ microk8s.kubectl wait --for=condition=ready pod -l k8s-app=kube-dns -n kube-system --timeout=180s
pod/coredns-7f9c69c78c-dbbb2 condition met
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
"DNS is enabled" is printed prematurely · Issue #2687 · canonical ...
When I run microk8s enable dns I see the following output: Enabling DNS # ... DNS is enabled However this is false: $...
Read more >Troubleshoot DNS Event ID 4013 - Windows Server
DNS Event ID 4013 in the DNS event log indicates that DNS service startup was delayed. It's because inbound replication of Active Directory ......
Read more >Troubleshooting - Cisco Umbrella Documentation
If the Umbrella roaming client (127.0.0.1 and/or ::1) is returning a public IP and querying the local DNS servers is returning a private...
Read more >What is a DNS server? - Cloudflare
DNS servers can fail for multiple reasons, such as power outages, cyber attacks, and hardware malfunctions. In the early days of the Internet,...
Read more >What is DNS and how does it work? - Network World.com
In the 1970s and early 80s, the task of matching domain names and IP addresses was assigned to one person - Elizabeth Feinler...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sed-i you could use the
microk8s kubectl rollout status
to wait for the deployment to finish.Sounds right