Bug 1731848

Summary: The provided APIs in kubefed-operator operator details information are not the real APIs provided by kubefed operator
Product: OpenShift Container Platform Reporter: Qin Ping <piqin>
Component: FederationAssignee: Aniket Bhat <anbhat>
Status: CLOSED WONTFIX QA Contact: Qin Ping <piqin>
Severity: medium Docs Contact:
Priority: high    
Version: 4.2.0CC: anbhat, nagrawal
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-30 18:06:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Qin Ping 2019-07-22 08:17:39 UTC 
Description of problem:
After the kubefed operator is deployed successfully, we can check the detailed information about the kubefed operator. Now, kubefed-operator's Provided APIs includes a lot of APIs which are the APIs provided by kubefed. Such as, ClusterPropagatedVersion, DNSEndpoint, ...


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-21-222447   True        False         3h40m   Cluster version is 4.2.0-0.nightly-2019-07-21-222447

kubefed-operator: 0.1.0


How reproducible:
100%


Steps to Reproduce:
1. Log into OCP web console with kubeadmin user
2. Create a namespace federation-system (Home->Projects->Create Project)
3. Install kubefed operator from OperatorHub(Operators->OperatorHub)
4. Check operator installation(Operators->Installed Operators->Kubefed Operator->Provided APIs)

Actual results:
There are 12 APIs, actually, only "KubeFed" API is provided by kubefed operator.


Expected results:


Additional info: