Closed bryonbaker closed 3 years ago
It appears there is mention of this requirement in the README for the repo (i.e. kubectl create -f deploy/crds/operator_v1alpha1_kubefed_cr.yaml -n kubefed-test
), and if that detail is missing from the operator docs that is definitely an oversight.
@bryonbaker We're working on updating the documentation for kubefed-operator on operatorhub.io
. You can track this PR #43 for more details.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
The documentation makes no mention that you need to deploy the control plane. It needs something like the following: Now we need to create a KubeFed resource to instantiate the KubeFed Controller in cluster scoped mode: