Bug 1737385 - The CRDs defined in the kubefed-operator are different with the CRDs used in kubefed
Summary: The CRDs defined in the kubefed-operator are different with the CRDs used in ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Federation
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
: 4.2.0
Assignee: Aniket Bhat
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-05 09:18 UTC by Qin Ping
Modified: 2019-10-16 06:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:34:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:34:53 UTC

Description Qin Ping 2019-08-05 09:18:14 UTC 
Description of problem:
The CRDs defined in the kubefed-operator are different with the CRDs used in kubefed

Version-Release number of selected component (if applicable):

https://github.com/openshift/kubefed-operator/tree/release-4.2/deploy/olm-catalog/kubefed-operator/4.2(commit: a3101552eb78449b7afbf5ef71f233fac240e826)

quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908041300-ose-kubefed


How reproducible:
100%

Steps to Reproduce:
1. 
2.
3.

Actual results:
The CRDs created with manifests from the kubefed-operator are:
$ oc get crd|grep kubefed
clusterpropagatedversions.core.kubefed.k8s.io               2019-08-05T08:37:32Z
dnsendpoints.multiclusterdns.kubefed.k8s.io                 2019-08-05T08:37:32Z
domains.multiclusterdns.kubefed.k8s.io                      2019-08-05T08:37:32Z
federatedservicestatuses.core.kubefed.k8s.io                2019-08-05T08:37:32Z
federatedtypeconfigs.core.kubefed.k8s.io                    2019-08-05T08:37:32Z
ingressdnsrecords.multiclusterdns.kubefed.k8s.io            2019-08-05T08:37:32Z
kubefedclusters.core.kubefed.k8s.io                         2019-08-05T08:37:32Z
kubefedconfigs.core.kubefed.k8s.io                          2019-08-05T08:37:32Z
kubefeds.operator.kubefed.io                                2019-08-05T08:37:32Z
kubefedwebhooks.operator.kubefed.io                         2019-08-05T08:37:32Z
propagatedversions.core.kubefed.k8s.io                      2019-08-05T08:37:32Z
replicaschedulingpreferences.scheduling.kubefed.k8s.io      2019-08-05T08:37:32Z
servicednsrecords.multiclusterdns.kubefed.k8s.io            2019-08-05T08:37:32Z

Some crds's group is xxx.kubefed.k8s.io, some crds's group is xxx.kubefed.io, seems for the kubefed, it's using the group xxx.kubefed.io.

So, when starting kubefed controller manager, we get the following error:
F0805 09:13:42.978529       1 controller-manager.go:221] Error retrieving KubeFedConfig "federation-system/kubefed": no matches for kind "KubeFedConfig" in version "core.kubefed.io/v1beta1"

Expected results:


Additional info:
Comment 1 Qin Ping 2019-08-07 06:12:16 UTC 
Verified with images:
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061459-ose-kubefed-operator
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061126-ose-kubefed
Comment 2 errata-xmlrpc 2019-10-16 06:34:43 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.