Open spowelljr opened 2 years ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Related to https://github.com/kubernetes/minikube/issues/15021
Currently, if a user is using
--driver=qemu
with--network=user
and-container-runtime=docker
and the firstnameserver
in their/etc/resolv.conf
on their host is an abnormal DNS (internal corp), minikube will start to fail and a take a long time to do so (~10 mins).This is too long to leave the user hanging, especially since there are no error messages provided to the user until around 5 minutes in.
The time to failure should be greatly increased and take around a minute and a half at the longest, but the faster the better.