In 0.22, we added support for networking/v1 Ingress API. This does not use the old and deprecated kubernetes.io/ingress.class annotation anymore to configure the Ingress class. Instead it has a dedicated ingressClassName in the spec. In 0.22, when the class field in the Ingress listener was configured, we set both at the same time - the annotation and the spec. But it turns out Kubernetes is rejecting this configuration and allows only one of these two to be used. This was not discovered initially in 0.22, since it seems to work fine when modifying the Ingress resource. Only creating new Ingress resource is rejected.