Details
-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
0
-
0%
-
Undefined
Description
Hi,
My customer sent me this case:
There's a mismatch between the apiVersion of an Ingress retrieved through kubectl versus retrieved through the console.
An ingress resource retrieved via kubectl shows apiVersion networking.k8s.io/v1:
apiVersion: networking.k8s.io/v1
kind: Ingress
name: keycloak
namespace: my-keycloak
spec:
rules:
- host: my-keycloak.apps.dev.example.com
http:
paths:
- backend:
service:
name: keycloak-http
port:
name: http
path: /
pathType: ImplementationSpecific
tls:
- hosts:
- my-keycloak.apps.dev.example.com
secretName: keycloak-tls
Whereas the same ingress shown in the console has apiVersion:
kind: Ingress
apiVersion: networking.k8s.io/v1beta1
name: keycloak
namespace: my-keycloak
spec:
tls:
- hosts:
- my-keycloak.apps.dev.example.com
secretName: keycloak-tls
rules:
- host: my-keycloak.apps.dev.example.com
http:
paths:
- path: /
pathType: ImplementationSpecific
backend:
serviceName: keycloak-http
servicePort: http
According to the api spec, ingresses in Openshift 4.7 should now use apiVersion v1 instead of v1beta:
Therefore, we'd expect both ways of retrieving the ingress to show apiVersion v1.
Could this be a bug or is there some configuration setting we might be missing?
We're also wondering if this might explain the large number of ingress events we're seeing or if that's caused by something else?