Description of problem: The "Enabling federation for new API types" part of the description of federation operator needs to be fixed Version-Release number of selected component (if applicable): oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.0-0.nightly-2019-05-14-202907 True False 11m Cluster version is 4.1.0-0.nightly-2019-05-14-202907 Operator version: 0.0.10 How reproducible: Steps to Reproduce: 1. Login into webconsole 2. Catalog->OperatorHub->Federation 3. "Enabling federation for new API types" part Actual results: kubectl get crd/federateddeployments.types.federation.k8s.io No resources found. Important Note: Federation of a CRD requires that the CRD be installed on all member clusters. If the CRD is not installed on a member cluster, propagation to that cluster will fail. Important Note: You must enable Federation support for Namespaces in this configuration before other types will work. Use kubefedctl enable namespaces. Expected results: 1.kubectl get crd/federateddeployments.types.federation.k8s.io NAME CREATED AT federateddeployments.types.federation.k8s.io 2019-05-15T05:30:34Z 2. CRD should be installed on host cluster and all target clusters. 3. enable Federation support for Namespaces/enable Federation support for Namespace Additional info:
This is fixed in the latest CSV description.
Verified with kubefed-operator v0.1.0
Does this bug require doc text? The Doc Type/Text field is not currently set. Thanks!
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