No matches for kind "Ingress" in version "networking.k8s.io/v1" #90077

vitalybibikov · 2020-04-11T10:24:51Z

I want to upgrade my cluster version from 1.15.10 to 1.16.7.
Prior to that I'm trying to update all the APIs.

Release notes to 1.16.0 state:
The following APIs are no longer served by default:

All resources under apps/v1beta1 and apps/v1beta2 - use apps/v1 instead
daemonsets, deployments, replicasets resources under extensions/v1beta1 - use apps/v1 instead
networkpolicies resources under extensions/v1beta1 - use networking.k8s.io/v1 instead
podsecuritypolicies resources under extensions/v1beta1 - use policy/v1beta1 instead

Release notes to 1.18.0 state:
The following deprecated APIs can no longer be served.

What happened:
When I change apiVersion in my Ingress from
apiVersion: networking.k8s.io/v1beta1
to
apiVersion: networking.k8s.io/v1

I get:
no matches for kind "Ingress" in version "networking.k8s.io/v1"

What you expected to happen:

Actually, I'm a bit of confused,
as currently kind: Ingress can only be served under v1beta1.

A PR #88509 states, that some changes had to be done, before graduation of the Ingress to v1.

So, the question is:
For now, I guess I should use --runtime-config apiserver flag to re-enable apis, but later?

How can I upgrade my cluster, if in 1.18.* v1beta1 is already deprecated, while kind:ingress is moved to v1 only in 1.19 (or later)?

Provider: Azure
Cluster Version: 1.15.10
Kubectl version: "v1.16.8". (tried on 1.15.5 and "v1.18.1") as well
OS: Windows 10 Pro, 1909 (18363.720)

The text was updated successfully, but these errors were encountered:

vitalybibikov · 2020-04-11T10:27:32Z

/sig network

athenabot · 2020-04-11T11:12:11Z

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

liggitt · 2020-04-11T22:15:15Z

Ingress is not yet available under networking.k8s.io/v1, the release note is for NetworkPolicy objects

zafercavdar · 2020-05-19T13:59:07Z

According to Kubernetes docs, ingress is available at networking.k8s.io/v1beta1

BorntraegerMarc · 2020-09-21T15:40:35Z

I'm a bit confused. Doesn't the official site say that we should use networking.k8s.io/v1?

liggitt · 2020-09-21T15:41:57Z

networking.k8s.io/v1 is available in Kubernetes v1.19+

cyclelabs-ryanberger · 2020-10-29T14:11:06Z

networking.k8s.io/v1beta1 == 1.14 to 1.18

networking.k8s.io/v1 = 1.19+

ygbingo · 2021-01-08T03:41:25Z

I got the same error . And this is my k8s version:

Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.10", GitCommit:"62876fc6d93e891aa7fbe19771e6a6c03773b0f7", GitTreeState:"clean", BuildDate:"2020-10-16T20:43:34Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

When I usr apiVersion: networking.k8s.io/v1
I got the error message:

error: unable to recognize ".\\dashboard-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"

And then I change my apiVersion to "networking.k8s.io/v1beta",
I got the error message like that

error: error validating ".\\dashboard-ingress.yaml": error validating data: ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "service" in io.k8s.api.networking.v1beta1.IngressBackend; if you choose to ignore these errors, turn validation off with --validate=false

Is that my format wrong？？

my-ingress.yaml

apiVersion: networking.k8s.io/v1beta
kind: Ingress
metadata:
  name: dashboard-ingress
  namespace: kube-dashboard
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - http:
        paths:
          - path: /dashboard
            pathType: Prefix
            backend:
              service:
                name: kubernetes-dashboard
                port:
                  number: 8080

kubernetes/kubernetes#90077 (comment)

* fix api version for ingress * Use v1beta1 for kubernetes version < 1.19 kubernetes/kubernetes#90077 (comment) * Update consul helm image version for tests * Add comment describing why we use KubeVersion to determine the apiVersion.

fongrx7 · 2021-01-27T16:54:54Z

I got the same error . And this is my k8s version:

Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.10", GitCommit:"62876fc6d93e891aa7fbe19771e6a6c03773b0f7", GitTreeState:"clean", BuildDate:"2020-10-16T20:43:34Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

When I usr apiVersion: networking.k8s.io/v1
I got the error message:

error: unable to recognize ".\\dashboard-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"

And then I change my apiVersion to "networking.k8s.io/v1beta",
I got the error message like that

error: error validating ".\\dashboard-ingress.yaml": error validating data: ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "service" in io.k8s.api.networking.v1beta1.IngressBackend; if you choose to ignore these errors, turn validation off with --validate=false

Is that my format wrong？？

my-ingress.yaml

apiVersion: networking.k8s.io/v1beta
kind: Ingress
metadata:
  name: dashboard-ingress
  namespace: kube-dashboard
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - http:
        paths:
          - path: /dashboard
            pathType: Prefix
            backend:
              service:
                name: kubernetes-dashboard
                port:
                  number: 8080

I have the same problem with 1.18, haven't found a solution yet

seadoherty · 2021-01-29T22:11:33Z

@fongrx7 sounds like we're in a similar spot.
Was able to get a little further but still wasn't 100% so if it helps...
Getting Version: 1.0.0 on http://172.17.0.3:31995/
Getting Version: 2.0.0 on posts.com/v2 (post.com is in etc/hosts as 172.17.0.3)
Was able to get there by creating a separate Service file

web-serv.yaml

apiVersion: v1
kind: Service
metadata:
  name: web-srv
spec:
  selector:
    app: posts
  ports:
    - name: posts
      protocol: TCP
      port: 8080
      targetPort: 8080

example-ingress.yaml:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: example-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: posts.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: web-srv
              servicePort: 8080
          - path: /v2
            pathType: Prefix
            backend:
              serviceName: web2
              servicePort: 8080

rohitdurvasula · 2021-02-24T20:43:46Z

@liggitt I am sure I am misinterpreting this, but why does a 1.18.1 kubectl recommend using networking.k8s.io/v1 if that is only available in 1.19+ ?

# kubectl version --short
Client Version: v1.18.1
Server Version: v1.18.1

# kubectl get --raw /apis/networking.k8s.io | jq .
{
  "kind": "APIGroup",
  "apiVersion": "v1",
  "name": "networking.k8s.io",
  "versions": [
    {
      "groupVersion": "networking.k8s.io/v1",
      "version": "v1"
    },
    {
      "groupVersion": "networking.k8s.io/v1beta1",
      "version": "v1beta1"
    }
  ],
  "preferredVersion": {
    "groupVersion": "networking.k8s.io/v1",
    "version": "v1"
  }
}

hoang-innomize · 2021-07-13T16:01:49Z

I also faced this issue when running with Kubernetes 1.18

Client Version: v1.19.7
Server Version: v1.18.16-eks-7737de

  "kind": "APIGroup",
  "apiVersion": "v1",
  "name": "networking.k8s.io",
  "versions": [
    {
      "groupVersion": "networking.k8s.io/v1",
      "version": "v1"
    },
    {
      "groupVersion": "networking.k8s.io/v1beta1",
      "version": "v1beta1"
    }
  ],
  "preferredVersion": {
    "groupVersion": "networking.k8s.io/v1",
    "version": "v1"
  }
}

So from what I can understand, we have to upgrade Kubernetes 1.19+ to get this works?

liggitt · 2021-07-13T16:04:11Z

yes, Ingress v1 only exists in 1.19+

hoang-innomize · 2021-07-13T16:05:48Z

Hmm, but I really confused about the log above, seems the v1 is there. And if we are using v1.18 we can change back to v1beta1 and it still works right?

liggitt · 2021-07-13T16:12:50Z

the networking.k8s.io/v1 group/version exists in 1.18, but only contains NetworkPolicy (https://github.com/kubernetes/api/blob/release-1.18/networking/v1/types.go)

This is for ingress as networking.k8s.io/v1 is supported from k8s 1.19, live-1 is 1.18. issue related to it: kubernetes/kubernetes#90077

bishal7679 · 2022-03-12T15:16:57Z

I want to create an ingress in kubernetes-dashboard but this giving me an error with the apiversion networking.k8s.io/v1beta1
how can resolve this @hoang-innomizetech @liggitt pls help me out

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: dashboard-ingress
namespace: kubernetes-dashboard
spec:
rules:

host: dashboard.com
http:
paths:
- backend:
  serviceName: kubernetes-dashboard
  servicePort: 80

theAkito · 2022-03-12T15:28:37Z

@bishal7679

Change the apiVersion's value to networking.k8s.io/v1.
Overhaul your current Ingress definition, to match the newest specification.

https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122

For example, you have to change servicePort to service.port.number and serviceName to service.name. You are also required to provide an explicit pathType, etc. All that is shown in the above link.

If you change everything according to the changes shown in the link, such a conversion works. I have tested it.

epochsupport · 2022-03-14T19:20:52Z

HI Team,

I want to route the request to external Load balancer of 3rd party vendor from the ingress/Service, Could you help on that

dem4gus · 2022-03-14T19:38:36Z

I'm not a member of the Kubernetes team so I obviously can't speak for them, but I don't think this issue is an appropriate place to be requesting support like that. You can refer to the Kubernetes documentation and the documentation for your 3rd party vendor if you need more help.

https://kubernetes.io/docs/concepts/services-networking/

decipher27 · 2022-06-15T17:06:38Z

Facing this while creating an Ingress
error: unable to recognize "es-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kots.io/app-slug: lite
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      more_set_headers "server: hide";
      more_set_headers "X-Content-Type-Options: nosniff";
      more_set_headers "X-Frame-Options: DENY";
      more_set_headers "X-Xss-Protection: 1";
      more_clear_headers Server;
  labels:
    app: atlas
    app.kubernetes.io/managed-by: Tiller
    kots.io/app-slug: lite
    kots.io/backup: velero
    release: ditto
  name: ditto-ing
  namespace: ditto
spec:
  rules:
  - host: <Domain> 
    http:
      paths:
      - backend:
          service:
            name: pok-ditto-service
            port:
              number: 3822
        path: /api/dito(/|$)(.*)
        pathType: Prefix
  tls:
  - hosts:
    - <Domain> 
    secretName: tls-wildcard-ditto

liggitt · 2022-06-15T17:07:37Z

Facing this while creating an Ingress
error: unable to recognize "es-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"

what server version are you running against (what does kubectl version show)?

v1 Ingress was added in 1.19.

decipher27 · 2022-06-15T17:22:15Z

❯ kubectl version --short
Client Version: v1.23.5
Server Version: v1.18.20-eks-154371

aojea · 2022-06-15T21:59:19Z

Server Version: v1.18.20-eks-154371

v1 Ingress was added in 1.19.

decipher27 · 2022-06-16T04:15:32Z

Still not able to create using the same kind and version.
Later created using apiVersion as networking.k8s.io/v1beta1 and some modifications to the spec.

aojea · 2022-06-16T07:18:43Z

v1 is not present on the server version you are using

kbansod · 2022-06-30T05:47:30Z

I am trying to change my template to use networking.k8s.io/v1 from networking.k8s.io/v1beta1

My pod gets created/deployed but it doesn't create any routes.

My ingress example is attached. I am not able to figure what would be missing. Please help me out.
ingress.yaml.txt

Environment details:

kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"878f5a8fe0d04ea70c5e5de11fa9cc7a49afb86e", GitTreeState:"clean", BuildDate:"2022-06-01T00:19:52Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5+3afdacb", GitCommit:"3c28e7a79b58e78b4c1dc1ab7e5f6c6c2d3aedd3", GitTreeState:"clean", BuildDate:"2022-05-10T16:30:48Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}

aojea · 2023-05-31T20:59:50Z

@marthasimons87 are you sure you are commenting on the right issue?

this is about Ingress and the problem is very clear

vitalybibikov added the kind/bug Categorizes issue or PR as related to a bug. label Apr 11, 2020

k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 11, 2020

k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 11, 2020

k8s-ci-robot added the triage/unresolved Indicates an issue that can not or will not be resolved. label Apr 11, 2020

liggitt closed this as completed Apr 11, 2020

NikitaGandhi mentioned this issue Jul 17, 2020

ingress is still serve using beta api version - revert previous change opendatacube/datacube-charts#167

Merged

Nuru mentioned this issue Nov 5, 2020

Need to include RBAC permissions for networking.k8s.io API stakater/Forecastle#128

Closed

Choongkyu mentioned this issue Jan 4, 2021

update Ingress config example to networking.k8s.io/v1beta1 until networking.k8s.io/v1 example supports Ingress kind kubernetes/website#25933

Closed

NoSkillGirl mentioned this issue Jan 7, 2021

[BUG] Kyverno CLI does not recognize Ingress kyverno/kyverno#1350

Closed

daxmc99 mentioned this issue Jan 8, 2021

Update ingress sourcegraph/deploy-sourcegraph#1586

Closed

2 tasks

thisisnotashwin added a commit to hashicorp/consul-helm that referenced this issue Jan 26, 2021

Use v1beta1 for kubernetes version < 1.19

ab2f62f

kubernetes/kubernetes#90077 (comment)

thisisnotashwin mentioned this issue Jan 26, 2021

fix api version for ingress hashicorp/consul-helm#786

Merged

2 tasks

thisisnotashwin added a commit to hashicorp/consul-helm that referenced this issue Jan 26, 2021

Use v1beta1 for kubernetes version < 1.19

afafa13

kubernetes/kubernetes#90077 (comment)

thisisnotashwin added a commit to hashicorp/consul-helm that referenced this issue Jan 26, 2021

Use v1beta1 for kubernetes version < 1.19

2066f11

kubernetes/kubernetes#90077 (comment)

thisisnotashwin added a commit to hashicorp/consul-helm that referenced this issue Jan 26, 2021

Use v1beta1 for kubernetes version < 1.19

9027b9c

kubernetes/kubernetes#90077 (comment)

thisisnotashwin added a commit to hashicorp/consul-helm that referenced this issue Jan 26, 2021

Use v1beta1 for kubernetes version < 1.19

3a014fb

kubernetes/kubernetes#90077 (comment)

thisisnotashwin added a commit to hashicorp/consul-helm that referenced this issue Jan 26, 2021

Use v1beta1 for kubernetes version < 1.19

3317c8f

kubernetes/kubernetes#90077 (comment)

wangcanfengxs mentioned this issue Jul 20, 2021

Error when use k8s 1.18, kind "Ingress" in version "networking.k8s.io/v1" goharbor/harbor-operator#705

Closed

nelson-lark mentioned this issue Aug 5, 2021

Check Ingress is managed by networking.k8s.io/v1 kiali/helm-charts#95

Merged

shurup mentioned this issue Sep 6, 2021

Fix v1beta1 API for Ingress resources in the Basic werf/website#246

Closed

samarpan-rai mentioned this issue Sep 6, 2021

Spring tutorial not working werf/website#247

Closed

afk11 mentioned this issue Oct 1, 2021

Invalid config for later kubernetes versions openMF/ph-ee-env-labs#3

Open

Nica-Alex mentioned this issue Oct 15, 2021

[kong] use latest available Ingress version Kong/charts#446

Merged

3 tasks

revolutionisme mentioned this issue Oct 20, 2021

Inferenceservice no url available, ready state is False with kserve RawDeployment mode kserve/kserve#1872

Closed

michael-burt mentioned this issue Nov 3, 2021

Error installing 2.0.0 with helm MoJo2600/pihole-kubernetes#168

Closed

This was referenced Dec 1, 2021

influxdb: support v1 ingress influxdata/helm-charts#352

Merged

Update ingress to v1 from v1beta1 for Influxdb2. influxdata/helm-charts#386

Merged

said-moj mentioned this issue Dec 2, 2021

LGA-1933 - Remove usage of deprecated extensions/v1beta1 ingress api version ministryofjustice/cla_backend#744

Closed

1 task

Hsankesara mentioned this issue Jan 7, 2022

No matches for kind "Ingress" in Kubernetes version > 1.18 RADAR-base/RADAR-Kubernetes#174

Closed

Thomah mentioned this issue Mar 14, 2022

#70 - email configuration cnieg/helm-charts#72

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No matches for kind "Ingress" in version "networking.k8s.io/v1" #90077

No matches for kind "Ingress" in version "networking.k8s.io/v1" #90077

vitalybibikov commented Apr 11, 2020

vitalybibikov commented Apr 11, 2020

athenabot commented Apr 11, 2020

liggitt commented Apr 11, 2020

zafercavdar commented May 19, 2020

BorntraegerMarc commented Sep 21, 2020 •

edited

Loading

liggitt commented Sep 21, 2020 •

edited

Loading

cyclelabs-ryanberger commented Oct 29, 2020

ygbingo commented Jan 8, 2021

fongrx7 commented Jan 27, 2021

seadoherty commented Jan 29, 2021

rohitdurvasula commented Feb 24, 2021

hoang-innomize commented Jul 13, 2021 •

edited

Loading

liggitt commented Jul 13, 2021

hoang-innomize commented Jul 13, 2021

liggitt commented Jul 13, 2021

bishal7679 commented Mar 12, 2022

theAkito commented Mar 12, 2022 •

edited

Loading

epochsupport commented Mar 14, 2022

dem4gus commented Mar 14, 2022

decipher27 commented Jun 15, 2022

liggitt commented Jun 15, 2022

decipher27 commented Jun 15, 2022

aojea commented Jun 15, 2022

decipher27 commented Jun 16, 2022

aojea commented Jun 16, 2022

kbansod commented Jun 30, 2022 •

edited

Loading

aojea commented May 31, 2023

No matches for kind "Ingress" in version "networking.k8s.io/v1" #90077

No matches for kind "Ingress" in version "networking.k8s.io/v1" #90077

Comments

vitalybibikov commented Apr 11, 2020

vitalybibikov commented Apr 11, 2020

athenabot commented Apr 11, 2020

liggitt commented Apr 11, 2020

zafercavdar commented May 19, 2020

BorntraegerMarc commented Sep 21, 2020 • edited Loading

liggitt commented Sep 21, 2020 • edited Loading

cyclelabs-ryanberger commented Oct 29, 2020

ygbingo commented Jan 8, 2021

fongrx7 commented Jan 27, 2021

seadoherty commented Jan 29, 2021

rohitdurvasula commented Feb 24, 2021

hoang-innomize commented Jul 13, 2021 • edited Loading

liggitt commented Jul 13, 2021

hoang-innomize commented Jul 13, 2021

liggitt commented Jul 13, 2021

bishal7679 commented Mar 12, 2022

theAkito commented Mar 12, 2022 • edited Loading

epochsupport commented Mar 14, 2022

dem4gus commented Mar 14, 2022

decipher27 commented Jun 15, 2022

liggitt commented Jun 15, 2022

decipher27 commented Jun 15, 2022

aojea commented Jun 15, 2022

decipher27 commented Jun 16, 2022

aojea commented Jun 16, 2022

kbansod commented Jun 30, 2022 • edited Loading

aojea commented May 31, 2023

BorntraegerMarc commented Sep 21, 2020 •

edited

Loading

liggitt commented Sep 21, 2020 •

edited

Loading

hoang-innomize commented Jul 13, 2021 •

edited

Loading

theAkito commented Mar 12, 2022 •

edited

Loading

kbansod commented Jun 30, 2022 •

edited

Loading