Description of problem: Recently, CRDs in openshift/api were migrated from version apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1. In the process, the IngressController's "scale" subresource was inadvertently removed. Version-Release number of selected component (if applicable): The erroneous CRD is not in current builds, but the problem can be reproduced by directly applying the CRD from Git. How reproducible: Easily. Steps to Reproduce: 1. Launch a cluster. 2. Apply the current IngressController CRD from Git: oc apply -f https://raw.githubusercontent.com/openshift/api/master/operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml 3. Try to scale the default ingresscontroller: oc -n openshift-ingress-operator scale ingresscontroller/default --replicas=2 Actual results: The `oc scale` command prints the following error message: Error from server (NotFound): ingresscontrollers.operator.openshift.io "default" not found Expected results: The `oc scale` command should print the following output: ingresscontroller.operator.openshift.io/default scaled Additional info: This commit mistakenly removed the IngressController CRD's "scale" subresource: https://github.com/openshift/api/pull/720/commits/fdbff4bcb56c5263cc7b8a740a3684ca9f4ba116#diff-c43b8f4ae306bf7ac8fbdde984579af1L16-L19
If possible, I would like to get this fixed in time to bump https://github.com/openshift/cluster-ingress-operator to use the updated CRD for 4.6. However, I do not believe this is a release blocker if the fix does not merge in time.
Retargeting to 4.6.0 to help land the PR. If it misses code-freeze, we can move this back to 4.7.0.
The PR merged and made into "4.6.0-0.nightly-2020-10-01-012547". The error is no more seen during scaling of controller with the latest CRD in place.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196