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

Add a module on installing with chectl on OCP 4. #1801

Merged
merged 6 commits into from
Jan 27, 2021
Merged

Add a module on installing with chectl on OCP 4. #1801

merged 6 commits into from
Jan 27, 2021

Conversation

yhontyk
Copy link

@yhontyk yhontyk commented Jan 20, 2021

Read our Contribution guide before submitting a PR.

What does this PR do?

What issues does this PR fix or reference?

Specify the version of the product this PR applies to.

PR Checklist

As the author of this Pull Request I made sure that:

  • vale has been run successfully against the PR branch
  • Link checker has been run successfully against the PR branch
  • Documentation describes a scenario that is already covered by QE tests, otherwise an issue has been created and acknowledged by Che QE team
  • Changed article references are updated where they are used (or a redirect has been set up on the docs side):

@yhontyk yhontyk requested review from tolusha and removed request for a team January 20, 2021 00:17
@yhontyk
Copy link
Author

yhontyk commented Jan 20, 2021

Hi @tolusha could you take a look when you have time? I used E2E tests as a reference but removed steps like disabling telemetry though - let me know if we should keep it or maybe add a note about it.
I also assume this procedure is the same for upstream and downstream so we can single-source the file.


.Prerequisites

* `oc` is installed on the cluster. See link:https://docs.openshift.com/container-platform/latest/cli_reference/openshift_cli/getting-started-cli.html#installing-the-cli[Installing the CLI].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't say that on the cluster is correct since it should be installed on the local machine for user to connect to cluster.


* `oc` is installed on the cluster. See link:https://docs.openshift.com/container-platform/latest/cli_reference/openshift_cli/getting-started-cli.html#installing-the-cli[Installing the CLI].

* `{prod-cli}` is installed on the cluster. See xref:using-the-chectl-management-tool.adoc[].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't say that on the cluster is correct since it should be installed on the local machine for user to deploy product on the cluster.


* `{prod-cli}` is installed on the cluster. See xref:using-the-chectl-management-tool.adoc[].

* __<namespace>__ represents the project of the target installation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not necessary since {prod-cli} will create namespace if it doesn't exist.

$ oc login
----

. Run the following command to verify that the version of the `oc` OpenShift CLI management tool is 4.6:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oc version command should be run before oc login

$ oc login
----

. Run the following command to verify that the version of the `oc` OpenShift CLI management tool is 4.6:
Copy link
Contributor

@tolusha tolusha Jan 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is better to say '...the version of the oc OpenShift CLI management tool matches OpenShift cluster version:'

.Procedure

. Log in to OpenShift. See link:https://docs.openshift.com/container-platform/4.6/cli_reference/openshift_cli/getting-started-cli.html#cli-logging-in_cli-developer-commands[Logging in to the CLI].
+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of having fixed version of OCP in the link we can use latest, for instance:
https://docs.openshift.com/container-platform/latest/cli_reference/openshift_cli/getting-started-cli.html#cli-logging-in_cli-developer-commands

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step is a prerequisite, it should move in the accurate section. Maybe refine "oc is available." to precise it should have same version as the target OpenShift cluster.

+
[subs="+quotes,+attributes",options="nowrap"]
----
$ {prod-cli} server:deploy -n _<namespace>_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-n _<namespace>_ isn't mandatory but it is better to use -n {prod-namespace}
Another point: chectl requires --platform openshift flag but crwctl doesn't need that.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tolusha thanks, I've addressed all comments above, and moved this command to a separate file so in the downstream we can define it with no flag.

@yhontyk yhontyk changed the title [WIP - Do not merge] Add a module on installing with chectl on OCP 4. Add a module on installing with chectl on OCP 4. Jan 20, 2021
@yhontyk
Copy link
Author

yhontyk commented Jan 22, 2021

@rkratky @themr0c @MichalMaler could smb please review this PR when you have time?

Client Version: 4.6.1
----

. Log in to OpenShift. See link:https://docs.openshift.com/container-platform/latest/cli_reference/openshift_cli/getting-started-cli.html#cli-logging-in_cli-developer-commands[Logging in to the CLI].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move to prerequites.

@themr0c themr0c self-assigned this Jan 26, 2021
@@ -0,0 +1,15 @@
:parent-context-of-installing-che-on-openshift-4-using-cli: {context}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the assembly has only one include, can we just omit it and have only the procedure?

@themr0c
Copy link
Contributor

themr0c commented Jan 26, 2021

We miss an entry in nav.adoc

@themr0c
Copy link
Contributor

themr0c commented Jan 26, 2021

Too many commits after last push. Can you rebase on upstream master again?

@themr0c
Copy link
Contributor

themr0c commented Jan 26, 2021

Can you try pass the vale checks using vale scoping? See: https://docs.errata.ai/vale/scoping#markup-based-configuration

@yhontyk yhontyk merged commit 41e2ef8 into eclipse-che:master Jan 27, 2021
@yhontyk yhontyk deleted the installingOnOpenShift4 branch January 27, 2021 08:35
@che-bot che-bot added this to the 7.26 milestone Jan 27, 2021
nickboldt pushed a commit that referenced this pull request Jan 29, 2021
* Add a module on installing with chectl on OCP 4.

* Put the whole codevlock in examples/

* endif to exceptions

* raise redbility grade

* change severity

* add links to ignore
nickboldt pushed a commit that referenced this pull request Jan 29, 2021
* Add a module on installing with chectl on OCP 4.

* Put the whole codevlock in examples/

* endif to exceptions

* raise redbility grade

* change severity

* add links to ignore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants