-
Notifications
You must be signed in to change notification settings - Fork 41.3k
Description
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
andapps/v1beta2
- useapps/v1
instead daemonsets
,deployments
,replicasets
resources underextensions/v1beta1
- useapps/v1
insteadnetworkpolicies
resources underextensions/v1beta1
- usenetworking.k8s.io/v1
insteadpodsecuritypolicies
resources underextensions/v1beta1
- usepolicy/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)