<p>I am using: 
<em>minikube version: v1.0.0</em>
I now need to create Ingress resource:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ingress
spec:
  backend:
    serviceName: testsvc
    servicePort: 80
</code></pre>

<p>and then I run <code>kubectl apply -f ./ingress.yaml</code></p>

<p>Error happened:</p>

<blockquote>
  <p>error: SchemaError(io.k8s.api.core.v1.CinderVolumeSource): invalid
  object doesn't have additional properties</p>
</blockquote>

<p>My kubectl version is:</p>

<p>Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:45:25Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}</p>

<p>After upgrading kubectl version to v1.14.0, I can create ingress with no problem. But now, the issue is ingress is NOT redirecting to pod:</p>

<p>this is my ingress.yaml:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
    name: dv
spec:
    rules:
    - host: ui.dv.com
      http:
          paths:
          - path: /
            backend:
                serviceName: ngsc
                servicePort: 3000
</code></pre>

<p>this is my service:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
    name: ngsc
spec:
    type: NodePort
    selector:
        app: ngsc
    ports:
    - port: 3000
      nodePort: 30080
      name: http
      targetPort: 3000
</code></pre>

<p>And this is my deployment:</p>

<pre><code>apiVersion: apps/v1beta1
kind: Deployment
metadata:
    name: ngsc
spec:
    replicas: 2
    template:
        metadata:
            name: ngsc
            labels:
                app: ngsc
        spec:
            containers:
            - image: myimage
              name: ngsc
              imagePullPolicy: IfNotPresent
</code></pre>

<p>I ave already added ui.dv.com into /etc/hosts, after I start all, and using curl <a href="http://ui.dv.com" rel="nofollow noreferrer">http://ui.dv.com</a>, there is no response</p>

<p>I checked the nginx log:</p>

<p>Error obtaining Endpoints for Service "default/ngsc": no object matching key "default/ngsc" in local store</p>

<p>for all pods, </p>

<pre><code>default       api-server-84dd8bcfc8-2hvlh                1/1     Running            26         3h23m
default       api-server-84dd8bcfc8-s697x                1/1     Running            28         3h23m
default       api-server-84dd8bcfc8-vq4vn                1/1     Running            26         3h23m
default       ngsc-559cbf57df-bcjb7                      1/1     Running            3          3h27m
default       ngsc-559cbf57df-j5v68                      1/1     Running            2          3h27m
kube-system   coredns-fb8b8dccf-ghj4l                    1/1     Running            42         36h
kube-system   coredns-fb8b8dccf-rwhw5                    1/1     Running            41         36h
kube-system   default-http-backend-6864bbb7db-p8fld      1/1     Running            47         36h
kube-system   etcd-minikube                              1/1     Running            3          36h
kube-system   kube-addon-manager-minikube                1/1     Running            4          36h
kube-system   kube-apiserver-minikube                    1/1     Running            27         36h
kube-system   kube-controller-manager-minikube           0/1     Error              4          11m
kube-system   kube-proxy-skn58                           1/1     Running            2          12h
kube-system   kube-scheduler-minikube                    0/1     CrashLoopBackOff   40         36h
kube-system   nginx-ingress-controller-f5744c676-j5r25   1/1     Running            47         3h16m
kube-system   storage-provisioner                        1/1     Running            7          36h
</code></pre>

<p>here, the ingress controller is running</p>

<p>now running:</p>

<p>kubectl describe pods -n kube-system nginx-ingress-controller-f5744c676-j5r25</p>

<p>I have this:</p>

<pre><code>Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Warning  Unhealthy  41m (x98 over 3h9m)    kubelet, minikube  Liveness probe failed: Get http://172.17.0.7:10254/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  25m (x208 over 3h10m)  kubelet, minikube  Readiness probe failed: Get http://172.17.0.7:10254/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  5m46s (x4 over 12m)    kubelet, minikube  Readiness probe failed: Get http://172.17.0.6:10254/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Warning  BackOff    35s (x448 over 3h3m)   kubelet, minikube  Back-off restarting failed container
</code></pre>

<p>describe ingress:</p>

<pre><code>Namespace:        default
Address:          
Default backend:  default-http-backend:80 ()
Rules:
  Host  Path  Backends
  ----  ----  --------
  *     
        /ui   ngsc:3000 (172.17.0.10:3000,172.17.0.7:3000)
  *     
        /api   api-server:8083 (172.17.0.5:8083,172.17.0.9:8083)
Annotations:
</code></pre>

<p>kubectl get ing
NAME        HOSTS   ADDRESS     PORTS   AGE
datavisor   *       10.0.2.15   80      3h12m</p>

<p>Finally:</p>

<p>curl <a href="http://10.0.2.15/ui" rel="nofollow noreferrer">http://10.0.2.15/ui</a></p>

<p>hanging, and stopped</p>

<p>Anything wrong here?</p>

user3006967
<p>There are no errors in your manifest, apparently, you are using wrong kubectl version.</p>

<p>kubectl needs to be within 1 minor from the cluster you are using as described <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/#before-you-begin" rel="nofollow noreferrer">here</a>.</p>

<blockquote>
  <p>You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. Using the latest version of kubectl helps avoid unforeseen issues.</p>
</blockquote>

<p>You can check your versions with</p>

<pre><code>kubectl version
</code></pre>
