Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] OpenShift 3 quickstart instructions for having multiple deployments doesn't do anything #17689

Closed
amisevsk opened this issue Aug 22, 2020 · 0 comments
Labels
area/doc Issues related to documentation area/install Issues related to installation, including offline/air gap and initial setup kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@amisevsk
Copy link
Contributor

Is your enhancement related to a problem? Please describe.

The section "Having multiple Che deployments" in the OpenShift 3 quickstart doesn't have enough detail to make sense; running the provided command simply prints that nothing happened:

$ oc patch clusterrolebinding che-operator \
    --type='json' \
    -p '[{"op": "add", "path": "/subjects/0", "value": {"kind":"ServiceAccount", "namespace": "chectl-test", "name": "che-operator"} }]'
clusterrolebinding.authorization.openshift.io/che-operator not patched

The original deploy command is

chectl server:start -n <namespace> -p openshift

as suggested in the doc.

Likely this section should just be removed, as Che installs will only support a single namespace in the near future (and so multiple deployments won't make sense).

Additional Info

Originally encountered while using downstream crwctl/2.3.0-GA-redhat.abf3efd linux-x64 node-v10.19.0, reproduced it with chectl/0.0.20200820-next.290685f linux-x64 node-v10.22.0

@amisevsk amisevsk added kind/enhancement A feature request - must adhere to the feature request template. area/doc Issues related to documentation area/install Issues related to installation, including offline/air gap and initial setup labels Aug 22, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 22, 2020
@ericwill ericwill removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 24, 2020
@tolusha tolusha added this to the 7.24 milestone Dec 16, 2020
@tolusha tolusha closed this as completed Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation area/install Issues related to installation, including offline/air gap and initial setup kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

4 participants