<p>I am trying to enable ingress in minkube. When I run <code>minikube addons enable ingress</code> it hangs for a while then I get the following error message:</p>
<pre><code>❌  Exiting due to MK_ADDON_ENABLE: run callbacks: running callbacks: [sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.15/kubectl apply -f /etc/kubernetes/addons/ingress-deploy.yaml: Process exited with status 1
stdout:
namespace/ingress-nginx unchanged
serviceaccount/ingress-nginx unchanged
configmap/ingress-nginx-controller unchanged
configmap/tcp-services unchanged
configmap/udp-services unchanged
clusterrole.rbac.authorization.k8s.io/ingress-nginx unchanged
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx unchanged
role.rbac.authorization.k8s.io/ingress-nginx unchanged
rolebinding.rbac.authorization.k8s.io/ingress-nginx unchanged
service/ingress-nginx-controller-admission unchanged

stderr:
error: error validating &quot;/etc/kubernetes/addons/ingress-deploy.yaml&quot;: error validating data: [ValidationError(Service.spec): unknown field &quot;ipFamilies&quot; in io.k8s.api.core.v1.ServiceSpec, ValidationError(Service.spec): unknown field &quot;ipFamilyPolicy&quot; in io.k8s.api.core.v1.ServiceSpec]; if you choose to ignore these errors, turn validation off with --validate=false
 waiting for app.kubernetes.io/name=ingress-nginx pods: timed out waiting for the condition]

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_addons_2c0e0cafd16ea0f95ac51773aeef036b316005b6_0.log                  │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯
</code></pre>
<p>This the the minikube start command I used:
<code>minikube start --kubernetes-version=v1.19.15 --vm-driver=docker</code></p>
<p>I have tried reinstalling minikube. It was working fine last week when I ran the same command.</p>
<p>If more specific information is needed please let me know and I will edit the question. Does anyone know how I could go about fixing this?</p>
<p>Thanks in advance.</p>

joe
<p>Bit late, but I hope someone find this useful, this happens becouse minikube could not pull the image(ingress-nginx-controller) in time, the way to know is:</p>
<pre><code>kubectl get pod -n ingress-nginx
</code></pre>
<p>If the ingress-nginx-controller-xxxx (xxxx is the identifier of the pod) has a status of ImagePullBackOff or something like that, you are on this scenario.</p>
<p>To fix you will need to first describe you pod:</p>
<pre><code>kubectl describe pod ingress-nginx-controller-xxxxx -n ingress-nginx
</code></pre>
<p>Look under containers/controller/images and copy its value(don't need to copyp the @sha256:... if it contains it). You must to manually pull it, but before probably delete the related deployment as well:</p>
<pre><code>kubectl delete deployment ingress-nginx-controller -n ingress-nginx
</code></pre>
<p>And then pull the image from the vm itself, in my case looks like this:</p>
<pre><code>minikube ssh docker pull k8s.gcr.io/ingress-nginx/controller:v1.2.1
</code></pre>
<p>Wait for it and then try to &quot;addons enable ingress&quot; again and see if it works, it did it for me.</p>
