<p>I have set up a Kubernetes cluster (a master and a worker) on two Centos 7 machines. They have the following IPs:<br />
Master: 192.168.1.40<br />
Worker: 192.168.1.41</p>
<p>They are accessible by SSH and I am not using a VPN. For both boxes, I have sudo access.</p>
<p>For the work I am doing, I had to add an Nginx Ingress Controller, which I did by doing:</p>
<pre><code>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.43.0/deploy/static/provider/baremetal/deploy.yaml
</code></pre>
<p>This yaml file seems fine to me and is a common one that occurs when trying to add an nginx ingress controller to a kubernetes cluster.</p>
<p>I don't see any errors when I do the above command.</p>
<p>However, when I try to install a helm configuration, such as:</p>
<pre><code>helm install dai eggplant/dai --version 0.6.5 -f dai.yaml --namespace dai
</code></pre>
<p>I am getting an error with my Nginx Ingress Controller:</p>
<pre><code>    W0119 11:58:00.550727   60628 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Error: Internal error occurred: failed calling webhook &quot;validate.nginx.ingress.kubernetes.io&quot;: Post &quot;https://ingress-nginx-controller-admission.ingress-nginx.svc:443/extensions/v1beta1/ingresses?timeout=30s&quot;: dial tcp 10.108.86.48:443: connect: connection refused
</code></pre>
<p>I think this is because of some kind of DNS error. I don't know where the IP 10.108.86.48:443 is coming from or how to find out.</p>
<p>I have also enabled a bunch of ports with firewall-cmd.</p>
<pre><code>    [root@manager-node ~]# sudo firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: ens33
  sources: 
  services: dhcpv6-client ssh
  ports: 6443/tcp 2379-2380/tcp 10250/tcp 10251/tcp 10252/tcp 10255/tcp 443/tcp 30154/tcp 31165/tcp
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
</code></pre>
<p>However, my nginx ingress pod doesn't seem to start either:</p>
<pre><code>    NAME                                       READY   STATUS              RESTARTS   AGE
ingress-nginx-controller-7bc44b4bb-rwmh2   0/1     ContainerCreating   0          19h
</code></pre>
<p>It remains as ContainerCreating for hours.</p>

PKen
<p>The issue is that as part of that <code>kubectl apply -f</code> you are also applying a <code>ValidatingWebhookConfiguration</code> (check the applied manifest file).</p>
<p>See <a href="https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook" rel="nofollow noreferrer">Using Admission Controllers | Kubernetes
Using Admission Controllers | Kubernetes</a> for more info.</p>
<p>The error you are seeing is because your Deployment is not starting up, and thus the ValidatingWebhook service configured as part of it isn't starting up either, so the Validating Controller in Kubernetes is failing every request.</p>
<pre class="lang-yaml prettyprint-override"><code>            - --validating-webhook=:8443
            - --validating-webhook-certificate=/usr/local/certificates/cert
            - --validating-webhook-key=/usr/local/certificates/key
</code></pre>
<p>Your pod is most likely not starting for another reason. More information is required to further debug.</p>
<p>I would recommend removing the <code>ValidatingWebhookConfiguration</code> from the applied manfiest.</p>
<p>You can also remove it manually with</p>
<pre class="lang-sh prettyprint-override"><code>kubectl delete ValidatingWebhookCOnfiguration ingress-nginx-admission
</code></pre>
<p>(Validating Controllers aren't namespaced)</p>
