search

openshift / kubefed-operator

Operator for Kubefed
Apache License 2.0
15 stars 15 forks source link

Documentation on operatorhub.io is incomplete #55

Closed bryonbaker closed 3 years ago

bryonbaker commented 5 years ago

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:

cat <<-EOF | oc apply -n <namespace> -f -
---
apiVersion: operator.kubefed.io/v1alpha1
kind: KubeFed
metadata:
  name: kubefed-resource
spec:
  scope: Cluster
---
EOF
marun commented 5 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.

sohankunkerkar commented 5 years ago

@bryonbaker We're working on updating the documentation for kubefed-operator on operatorhub.io. You can track this PR #43 for more details.

openshift-bot commented 4 years ago

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

openshift-bot commented 4 years ago

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

openshift-bot commented 3 years ago

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-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/kubefed-operator/issues/55#issuecomment-726790667): >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 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.