Open hugodopradofernandes opened 2 years ago
Also other fields with issues: https://stackoverflow.com/questions/64125048/get-error-unknown-field-servicename-in-io-k8s-api-networking-v1-ingressbacken
I recommend also fixing these
Ingress
and IngressClass
resources have graduated to networking.k8s.io/v1
. Ingress and IngressClass types in the extensions/v1beta1
and networking.k8s.io/v1beta1
API versions are deprecated and will no longer be served in 1.22+. Persisted objects can be accessed via the networking.k8s.io/v1
API. Notable changes in v1 Ingress objects (v1beta1 field names are unchanged):
spec.backend
-> spec.defaultBackend
serviceName
-> service.name
servicePort
-> service.port.name
(for string values)servicePort
-> service.port.number
(for numeric values)pathType
no longer has a default value in v1; "Exact", "Prefix", or "ImplementationSpecific" must be specified
Other Ingress API updates:path
is no longer required to be a valid regular expression
fix ingress API for k8s > 1.22. Current value is deprecated https://kubernetes.io/docs/reference/using-api/deprecation-guide/
Ingress
The extensions/v1beta1 and networking.k8s.io/v1beta1 API versions of Ingress is no longer served as of v1.22.