Description of problem: Installed the kubefed operator with "All namespaces on the cluster" mode, the operator installed successfully, but when trying to deploy kubefed control plane under federation-system namespace, the kubefed control plane deployment failed. Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-07-22-202159 True False 4h30m Cluster version is 4.2.0-0.nightly-2019-07-22-202159 kubefed-operator: v0.1.0 How reproducible: 100% Steps to Reproduce: 1. Login into web console with kubeadmin user 2. Install kubefed operator with "All namespaces on the cluster" mode(Operators->OperatorHub) 3. Create a project federation-system(Home->Projects) 4. Create a kubefed instance in federation-system namespace apiVersion: operator.kubefed.io/v1alpha1 kind: KubeFed metadata: name: kubefed namespace: federation-system spec: scope: Cluster 5. Check deployment of kubefed control plane Actual results: kubefed control plane is not installed as expected. $ oc get deployment -n federation-system No resources found. Expected results: kubefed control plane is installed successfully. Additional info: 1. kubefed operator is installed under openshift-operators namespace $ oc get deployment -n openshift-operators NAME READY UP-TO-DATE AVAILABLE AGE kubefed-operator 1/1 1 1 12m 2. If creating kubefed instance under openshift-operators namespace, kubefed control plane can be deployed under openshift-operators namespace $ oc get kubefed kubefed -n openshift-operators -oyaml apiVersion: operator.kubefed.io/v1alpha1 kind: KubeFed metadata: creationTimestamp: "2019-07-23T07:08:10Z" generation: 1 name: kubefed namespace: openshift-operators resourceVersion: "93668" selfLink: /apis/operator.kubefed.io/v1alpha1/namespaces/openshift-operators/kubefeds/kubefed uid: a10c68c3-ad18-11e9-b79b-0a2401d2c6e6 spec: scope: Cluster status: version: 0.1.0 $ oc get deployment -n openshift-operators NAME READY UP-TO-DATE AVAILABLE AGE kubefed-controller-manager 2/2 2 2 36s kubefed-operator 1/1 1 1 13m
I think our intention is to only support cluster-scoped kubefed deployed to the kube-federation-system namespace. I don't think it matters whether this restriction is in code or documentation. Has deployment to the kube-federation-system namespace been validated?
This issue should be fixed after this PR is merged. https://github.com/openshift/kubefed-operator/pull/19
Verified with images: quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061126-ose-kubefed quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061459-ose-kubefed-operator
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, 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-2019:2922