Hide Forgot
Description of problem: kubefed operator should install cluster scoped kubefed webhook in the "openshift-federation-system" namespace Version-Release number of selected component (if applicable): quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908131437-ose-kubefed-operator How reproducible: 100% Steps to Reproduce: 1. Installed kubefed operator 2. Created a kubefedwebhook object to deploy a clusters scoped kubefed webhook 3. Actual results: The default yaml file we can get from web console is: apiVersion: operator.kubefed.io/v1alpha1 kind: KubeFedWebHook metadata: name: kubefedwebhook-resource namespace: default spec: scope: Cluster apiVersion: operator.kubefed.io/v1alpha1 kind: KubeFedWebHook metadata: name: kubefedwebhook-resource namespace: default spec: scope: Cluster The the cluster scoped kubefed webhook will be installed under default project. Expected results: The cluster scoped kubefed webhook can and only can be installed under the "openshift-federation-system" project. If the openshift-federation-system project is not exist, kubefed operator can create it first. Additional info:
Hi Ping, We're planning to get rid of the scope field from the KubefedWebHook CR, however, we're not going to restrict the users to deploy a KubeFedWebHook controller pod in the `openshift-federation-system` namespace. Having said that, we'll be documenting the steps in the CSV description/openshift docs to inform users the recommended way to install a KubeFedWebHook controller pod in a given canonical namespace. You can track this PR: https://github.com/openshift/openshift-docs/pull/16256/files#r315769990 for more information.
Hi Sohan, there still something needs to fix for this issue. 1. The default kubefed-namespace in kubefedctl should be "openshift-federation-system" not "kube-federation-system" 2. When creating kubefedwebhook instance from web console, the kubefedwebhook.spec should be null.
Hi Ping, PFB my inline response. 1. The default kubefed-namespace in kubefedctl should be "openshift-federation-system" not "kube-federation-system" Sohan: I will sync with you on this point later tonight (your morning). 2. When creating kubefedwebhook instance from web console, the kubefedwebhook.spec should be null. Sohan: This is fixed in the latest community-operators PR which is merged today
As discussed, I'm moving this BZ to modified as there's a separate BZ for the first point.
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