You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cli_reference/index.adoc
+1-8Lines changed: 1 addition & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,9 @@ A user performs a range of operations while working on {product-title} such as t
10
10
11
11
* Managing clusters
12
12
* Building, deploying, and managing applications
13
-
ifndef::microshift[]
14
13
* Managing deployment processes
15
14
* Developing Operators
16
15
* Creating and maintaining Operator catalogs
17
-
endif::[]
18
16
19
17
{product-title} offers a set of command-line interface (CLI) tools that simplify these tasks by enabling users to perform various administration and development operations from the terminal.
20
18
These tools expose simple commands to manage the applications, as well as interact with each component of the system.
@@ -24,17 +22,12 @@ These tools expose simple commands to manage the applications, as well as intera
24
22
25
23
The following set of CLI tools are available in {product-title}:
26
24
27
-
* xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[OpenShift CLI (oc)]: This is the most commonly used CLI tool by {product-title} users. It helps both cluster administrators and developers to perform end-to-end operations across {product-title} using the terminal.
28
-
ifndef::microshift[]
29
-
Unlike the web console, it allows the user to work directly with the project source code using command scripts.
30
-
endif::microshift[]
25
+
* xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[OpenShift CLI (oc)]: This is the most commonly used CLI tool by {product-title} users. It helps both cluster administrators and developers to perform end-to-end operations across {product-title} using the terminal. Unlike the web console, it allows the user to work directly with the project source code using command scripts.
31
26
32
-
ifndef::microshift[]
33
27
* xref:../cli_reference/kn-cli-tools.adoc#kn-cli-tools[Knative CLI (kn)]: The Knative (`kn`) CLI tool provides simple and intuitive terminal commands that can be used to interact with OpenShift Serverless components, such as Knative Serving and Eventing.
34
28
35
29
* xref:../cli_reference/tkn_cli/installing-tkn.adoc#installing-tkn[Pipelines CLI (tkn)]: OpenShift Pipelines is a continuous integration and continuous delivery (CI/CD) solution in {product-title}, which internally uses Tekton. The `tkn` CLI tool provides simple and intuitive commands to interact with OpenShift Pipelines using the terminal.
36
30
37
31
* xref:../cli_reference/opm/cli-opm-install.adoc#cli-opm-install[opm CLI]: The `opm` CLI tool helps the Operator developers and cluster administrators to create and maintain the catalogs of Operators from the terminal.
38
32
39
33
* xref:../cli_reference/osdk/cli-osdk-install.adoc#cli-osdk-install[Operator SDK]: The Operator SDK, a component of the Operator Framework, provides a CLI tool that Operator developers can use to build, test, and deploy an Operator from the terminal. It simplifies the process of building Kubernetes-native applications, which can require deep, application-specific operational knowledge.
A user builds, deploys, and manages boths applications and clusters while working with {product-title}.
10
+
11
+
{product-title} can use different command-line interface (CLI) tools that simplify these tasks by enabling users to perform various administration and development operations from the terminal.
12
+
These tools expose simple commands to manage the deployments, as well as interact with each component of the system.
13
+
14
+
In addition to built-in `microshift` command types and Linux CLI tools, the optional OpenShift CLI (`oc`) tool with an enabled subset of commands is available for you to use if you are already familiar with {OCP} and Kubernetes.
15
+
//more info on these tools is expected in the future, hence this overview assembly
16
+
17
+
[role="_additional-resources"]
18
+
[id="additional-resources_cli-tools-overview"]
19
+
.Additional resources
20
+
21
+
* link:https://access.redhat.com/documentation/en-us/microshift/4.12/html/microshift_cli_ref/microshift-cli-using-oc.adoc#microshift-cli-oc-about[Installing the `oc` tool for MicroShift].
22
+
23
+
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html/cli_tools/openshift-cli-oc[OpenShift CLI (oc)]: A full description of `oc` as provided by the {OCP} documentation. Commands focused on multi-node deployments, projects, and developer tooling are not supported by {product-title}.
24
+
25
+
* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9[Red Hat Enterprise Linux (RHEL)]: The RHEL documentation for your specific use case.
26
+
//NEED INFO: drill down to more specific links within RHEL docs
This reference provides descriptions and example commands for OpenShift CLI (`oc`) commands. You must have `cluster-admin` or equivalent permissions to use these commands.
10
+
11
+
Run `oc adm -h` to list all administrator commands or run `oc <command> --help` to get additional details for a specific command.
12
+
13
+
[IMPORTANT]
14
+
====
15
+
Using `oc <command> --help` lists details for any `oc` command. Not all `oc` commands apply to using {product-title}.
16
+
====
17
+
18
+
// The OCP file is auto-generated from the openshift/oc repository; MicroShift is made manually
0 commit comments