Description of problem: The federateddeployments crd's group should be types.federation.k8s.io not primitives.federation.k8s.io in federation installation UI Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-19-004004 True False 3h39m Cluster version is 4.0.0-0.nightly-2019-03-19-004004 Federation v2 controller-manager version: version.Info{Version:"0.0.6", GitCommit:"de6a0a909418f5ddf2d04d232b0ca55aa9cffb49", GitTreeState:"clean", BuildDate:"2019-03-14T00:43:37Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} How reproducible: 100% Steps to Reproduce: 1. Login webconsole with kubeadmin user 2. Catalog->OperatorHub->Federation In the install UI, chapter: Enabling federation for new API types Running this command produces a new CRD in the hosting cluster to be the federation API surface for the deployments resource. kubectl get crd/federateddeployments.primitives.federation.k8s.io No resources found.
This will be fixed in 0.0.7 release of the operator :)
Should be fixed in 0.0.7 CSV
Verification failed with: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.ci-2019-03-31-223338 True False 91m Cluster version is 4.0.0-0.ci-2019-03-31-223338 Federation v2 controller-manager version: version.Info{Version:"v0.0.7", GitCommit:"3e251608ca5357080b95a0bedc45759652f17d29", GitTreeState:"clean", BuildDate:"2019-03-22T22:30:26Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"} Still need some updates for "Enabling federation for new API types" part: 1. change 'kubefed2 enable deployments.extensions \ --federation-namespace=' to 'kubefed2 enable deployments.extensions --federation-namespace=<namespace>' 2. change kubectl get crd/federateddeployments.types.federation.k8s.io No resources found. to kubectl get crd/federateddeployments.types.federation.k8s.io -n <namespace> NAME CREATED AT federateddeployments.types.federation.k8s.io 2019-04-01T04:54:19Z
(In reply to Qin Ping from comment #4) > Verification failed with: > $ oc get clusterversion > NAME VERSION AVAILABLE PROGRESSING SINCE > STATUS > version 4.0.0-0.ci-2019-03-31-223338 True False 91m > Cluster version is 4.0.0-0.ci-2019-03-31-223338 > > Federation v2 controller-manager version: version.Info{Version:"v0.0.7", > GitCommit:"3e251608ca5357080b95a0bedc45759652f17d29", GitTreeState:"clean", > BuildDate:"2019-03-22T22:30:26Z", GoVersion:"go1.11.2", Compiler:"gc", > Platform:"linux/amd64"} > > Still need some updates for "Enabling federation for new API types" part: > 1. change 'kubefed2 enable deployments.extensions \ --federation-namespace=' > to 'kubefed2 enable deployments.extensions > --federation-namespace=<namespace>' > 2. change > kubectl get crd/federateddeployments.types.federation.k8s.io > No resources found. > to > kubectl get crd/federateddeployments.types.federation.k8s.io -n <namespace> > NAME CREATED AT > federateddeployments.types.federation.k8s.io 2019-04-01T04:54:19Z Where is 'Enabling federation for new API types'? I don't think every documented command should have to specify `--federation-namespace`, since a deployment using the default namespace (federation-system) does not require the argument. I think it would make more sense to document the requirement to provide --federation-namespace where the federation namespace is not the default.
Ping is referring to content in the CSV description: https://operatorhub.io/operator/federation.v0.0.7 Ping, it looks like this is a really weird formatting bug. I'm in touch with the OLM team about it; unfortunately it looks like our CSV crashes the preview tool at: https://operatorhub.io/preview
Yes, a weird formatting bug. Seems "kubefed2 enable deployments.extensions --federation-namespace=<namespace\>" can fix it, but I don't know why. Cause "kubefed2 enable deployments.extensions --federation-namespace=<namespace>" is good enough from the Markdown syntax.
I think this is fixed in the latest version of kubefed-operator.