Skip to content

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

@vitalybibikov

Description

@vitalybibikov

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.sig/networkCategorizes an issue or PR as relevant to SIG Network.triage/unresolvedIndicates an issue that can not or will not be resolved.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions