mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
OSDOCS#15974: Removing unused assemblies (Control plane pod)
This commit is contained in:
Andrea Hoffer
@@ -1,27 +0,0 @@
|
||||
////
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id='configuring-the-odo-cli']
|
||||
= Configuring the odo CLI
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: configuring-the-odo-cli
|
||||
|
||||
toc::[]
|
||||
|
||||
// Comment out per https://issues.redhat.com/browse/RHDEVDOCS-3594
|
||||
// include::modules/developer-cli-odo-using-command-completion.adoc[leveloffset=+1]
|
||||
|
||||
You can find the global settings for `odo` in the `preference.yaml` file which is located by default in your `$HOME/.odo` directory.
|
||||
|
||||
You can set a different location for the `preference.yaml` file by exporting the `GLOBALODOCONFIG` variable.
|
||||
|
||||
// view config
|
||||
include::modules/developer-cli-odo-view-config.adoc[leveloffset=+1]
|
||||
// set key
|
||||
include::modules/developer-cli-odo-set-config.adoc[leveloffset=+1]
|
||||
// unset key
|
||||
include::modules/developer-cli-odo-unset-config.adoc[leveloffset=+1]
|
||||
// preference ref table
|
||||
include::modules/developer-cli-odo-preference-table.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-ignoring-files-or-patterns.adoc[leveloffset=+1]
|
||||
////
|
||||
@@ -1,22 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id=creating-instances-of-services-managed-by-operators]
|
||||
= Creating instances of services managed by Operators
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-instances-of-services-managed-by-operators
|
||||
|
||||
toc::[]
|
||||
|
||||
Operators are a method of packaging, deploying, and managing Kubernetes services. With `{odo-title}`, you can create instances of services from the custom resource definitions (CRDs) provided by the Operators. You can then use these instances in your projects and link them to your components.
|
||||
|
||||
To create services from an Operator, you must ensure that the Operator has valid values defined in its `metadata` to start the requested service. `{odo-title}` uses the `metadata.annotations.alm-examples` YAML file of an Operator to start
|
||||
the service. If this YAML has placeholder values or sample values, a service cannot start. You can modify the YAML file and start the service with the modified values. To learn how to modify YAML files and start services from it, see xref:../../cli_reference/developer_cli_odo/creating-instances-of-services-managed-by-operators.adoc#creating-services-from-yaml-files_creating-instances-of-services-managed-by-operators[Creating services from YAML files].
|
||||
|
||||
== Prerequisites
|
||||
* Install the `oc` CLI and log in to the cluster.
|
||||
** Note that the configuration of the cluster determines the services available to you. To access the Operator services, a cluster administrator must install the respective Operator on the cluster first. To learn more, see xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-operators-from-operatorhub_olm-adding-operators-to-a-cluster[Adding Operators to the cluster].
|
||||
* Install the `{odo-title}` CLI.
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-listing-available-services-from-the-operators-installed-on-the-cluster.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-creating-a-service-from-an-operator.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-creating-services-from-yaml-files.adoc[leveloffset=+1]
|
||||
@@ -1,23 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id=creating-a-java-application-with-a-database]
|
||||
= Creating a Java application with a database
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-a-java-application-with-a-database
|
||||
toc::[]
|
||||
|
||||
This example describes how to deploy a Java application by using devfile and connect it to a database service.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* A running cluster.
|
||||
* `{odo-title}` is installed.
|
||||
* A Service Binding Operator is installed in your cluster. To learn how to install Operators, contact your cluster administrator or see xref:../../../operators/user/olm-installing-operators-in-namespace.adoc#olm-installing-operators-from-operatorhub_olm-installing-operators-in-namespace[Installing Operators from OperatorHub].
|
||||
* A Dev4Devs PostgreSQL Operator Operator is installed in your cluster. To learn how to install Operators, contact your cluster administrator or see xref:../../../operators/user/olm-installing-operators-in-namespace.adoc#olm-installing-operators-from-operatorhub_olm-installing-operators-in-namespace[Installing Operators from OperatorHub].
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-java-microservice-jpa-application.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-database-with-odo.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-connecting-a-java-application-to-mysql-database.adoc[leveloffset=+1]
|
||||
@@ -1,31 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
[id='creating-a-multicomponent-application-with-odo']
|
||||
= Creating a multicomponent application with `{odo-title}`
|
||||
:context: creating-a-multicomponent-application-with-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` allows you to create a multicomponent application, modify it, and link its components in an easy and automated way.
|
||||
|
||||
This example describes how to deploy a multicomponent application - a shooter game. The application consists of a front-end Node.js component and a back-end Java component.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* `{odo-title}` is installed.
|
||||
* You have a running cluster. Developers can use link:https://access.redhat.com/documentation/en-us/red_hat_openshift_local/[{openshift-local-productname}] to deploy a local cluster quickly.
|
||||
* Maven is installed.
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deploying-the-back-end-component.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deploying-the-front-end-component.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-linking-both-components.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-exposing-the-components-to-the-public.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-modifying-the-running-application.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deleting-an-application.adoc[leveloffset=+1]
|
||||
@@ -1,29 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
[id='creating-a-single-component-application-with-odo']
|
||||
= Creating a single-component application with {odo-title}
|
||||
|
||||
:context: creating-a-single-component-application-with-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
With `{odo-title}`, you can create and deploy applications on clusters.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* `{odo-title}` is installed.
|
||||
* You have a running cluster. You can use link:https://access.redhat.com/documentation/en-us/red_hat_openshift_local/[{openshift-local-productname}] to deploy a local cluster quickly.
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-creating-and-deploying-a-nodejs-application-with-odo.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-modifying-your-application-code.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-adding-storage-to-the-application-components.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-adding-a-custom-builder-to-specify-a-build-image.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-connecting-your-application-to-multiple-services-using-openshift-service-catalog.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deleting-an-application.adoc[leveloffset=+1]
|
||||
@@ -1,31 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id=creating-an-application-with-a-database]
|
||||
= Creating an application with a database
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-an-application-with-a-database
|
||||
|
||||
toc::[]
|
||||
|
||||
This example describes how to deploy and connect a database to a front-end application.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* `{odo-title}` is installed.
|
||||
* `oc` client is installed.
|
||||
* You have a running cluster. Developers can use link:https://access.redhat.com/documentation/en-us/red_hat_openshift_local/[{openshift-local-productname}] to deploy a local cluster quickly.
|
||||
* The Service Catalog is installed and enabled on your cluster.
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
Service Catalog is deprecated on {product-title} 4 and later.
|
||||
====
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deploying-the-front-end-component.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deploying-a-database-in-interactive-mode.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-deploying-a-database-manually.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-connecting-the-database.adoc[leveloffset=+1]
|
||||
@@ -1,14 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
[id='debugging-applications-in-odo']
|
||||
= Debugging applications in `{odo-title}`
|
||||
:context: debugging-applications-in-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
With `{odo-title}`, you can attach a debugger to remotely debug your application. This feature is only supported for NodeJS and Java components.
|
||||
|
||||
Components created with `{odo-title}` run in the debug mode by default. A debugger agent runs on the component, on a specific port. To start debugging your application, you must start port forwarding and attach the local debugger bundled in your Integrated development environment (IDE).
|
||||
|
||||
include::modules/developer-cli-odo-debugging-an-application.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-configuring-debugging-parameters.adoc[leveloffset=+1]
|
||||
@@ -1,11 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id='deleting-applications']
|
||||
= Deleting applications
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: deleting-applications
|
||||
|
||||
toc::[]
|
||||
|
||||
You can delete applications and all components associated with the application in your project.
|
||||
|
||||
include::modules/developer-cli-odo-deleting-an-application.adoc[leveloffset=+1]
|
||||
@@ -1,37 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="sample-applications"]
|
||||
= Sample applications
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: using-sample-applications
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` offers partial compatibility with any language or runtime listed within the {product-title} catalog of component types. For example:
|
||||
|
||||
[source,terminal]
|
||||
----
|
||||
NAME PROJECT TAGS
|
||||
dotnet openshift 3.1,latest
|
||||
httpd openshift 2.4,latest
|
||||
java openshift 8,latest
|
||||
nginx openshift 1.10,1.12,1.8,latest
|
||||
nodejs openshift 0.10,4,6,8,latest
|
||||
perl openshift 5.16,5.20,5.24,latest
|
||||
php openshift 5.5,5.6,7.0,7.1,latest
|
||||
python openshift 2.7,3.3,3.4,3.5,3.6,latest
|
||||
ruby openshift 2.0,2.2,2.3,2.4,latest
|
||||
wildfly openshift 10.0,10.1,8.1,9.0,latest
|
||||
----
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
For `{odo-title}` Java and Node.js are the officially supported component types.
|
||||
Run `odo catalog list components` to verify the officially supported component types.
|
||||
====
|
||||
|
||||
To access the component over the web, create a URL using `odo url create`.
|
||||
|
||||
|
||||
|
||||
include::modules/developer-cli-odo-sample-applications-git.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-sample-applications-binary.adoc[leveloffset=+1]
|
||||
@@ -1,29 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="using-devfiles-in-odo"]
|
||||
= Using devfiles in {odo-title}
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-applications-by-using-devfiles
|
||||
|
||||
toc::[]
|
||||
|
||||
include::modules/developer-cli-odo-about-devfiles-in-odo.adoc[leveloffset=+1]
|
||||
|
||||
== Creating a Java application by using a devfile
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* You have installed `{odo-title}`.
|
||||
* You must know your ingress domain cluster name. Contact your cluster administrator if you do not know it. For example, `apps-crc.testing` is the cluster domain name for https://access.redhat.com/documentation/en-us/red_hat_openshift_local/[{openshift-local-productname}].
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Currently odo does not support creating devfile components with `--git` or `--binary` flags. You can only create S2I components when using these flags.
|
||||
====
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/developer-cli-odo-listing-available-devfile-components.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/developer-cli-odo-deploying-a-java-application-using-a-devfile.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/developer-cli-odo-converting-an-s2i-component-into-a-devfile-component.adoc[leveloffset=+1]
|
||||
@@ -1,11 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="working-with-projects"]
|
||||
= Working with projects
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: working-with-projects
|
||||
|
||||
toc::[]
|
||||
|
||||
Project keeps your source code, tests, and libraries organized in a separate single unit.
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project.adoc[leveloffset=+1]
|
||||
@@ -1,21 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id='working-with-storage']
|
||||
= Working with storage
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: working-with-storage
|
||||
|
||||
toc::[]
|
||||
|
||||
Persistent storage keeps data available between restarts of `{odo-title}`.
|
||||
|
||||
include::modules/developer-cli-odo-adding-storage-to-the-application-components.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-adding-storage-to-a-specific-container.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-switching-between-ephemeral-and-persistent-storage.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../../storage/understanding-ephemeral-storage.adoc#storage-ephemeral-storage-overview_understanding-ephemeral-storage[Understanding ephemeral storage].
|
||||
* xref:../../../storage/understanding-persistent-storage.adoc#persistent-storage-overview_understanding-persistent-storage[Understanding persistent storage]
|
||||
@@ -1,30 +0,0 @@
|
||||
////
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id='installing-odo']
|
||||
= Installing odo
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
// The following section describes how to install `{odo-title}` on different platforms using the CLI or the Visual Studio Code (VS Code) IDE.
|
||||
|
||||
You can install the `{odo-title}` CLI on Linux, Windows, or macOS by downloading a binary. You can also install the OpenShift VS Code extension, which uses both the `{odo-title}` and the `oc` binaries to interact with your OpenShift Container Platform cluster. For {op-system-base-full}, you can install the `{odo-title}` CLI as an RPM.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Currently, `{odo-title}` does not support installation in a restricted network environment.
|
||||
====
|
||||
|
||||
// You can also find the URL to the latest binaries from the {product-title} web console by clicking the *?* icon in the upper-right corner and selecting *Command Line Tools*
|
||||
|
||||
include::modules/developer-cli-odo-installing-odo-on-linux.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-installing-odo-on-windows.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-installing-odo-on-macos.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-installing-odo-on-vs-code.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-installing-odo-on-linux-rpm.adoc[leveloffset=+1]
|
||||
////
|
||||
@@ -1,11 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id='managing-environment-variables']
|
||||
= Managing environment variables
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: managing-environment-variables
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` stores component-specific configurations and environment variables in the `config` file. You can use the `odo config` command to set, unset, and list environment variables for components without the need to modify the `config` file.
|
||||
|
||||
include::modules/developer-cli-odo-setting-and-unsetting-environment-variables.adoc[leveloffset=+1]
|
||||
@@ -1,17 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="odo-architecture"]
|
||||
= odo architecture
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: odo-architecture
|
||||
|
||||
toc::[]
|
||||
|
||||
This section describes `{odo-title}` architecture and how `{odo-title}` manages resources on a cluster.
|
||||
|
||||
include::modules/developer-cli-odo-developer-setup.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-openshift-source-to-image.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-openshift-cluster-objects.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-push-workflow.adoc[leveloffset=+1]
|
||||
|
||||
// [role="_additional-resources"]
|
||||
// == Additional resources
|
||||
@@ -1,21 +0,0 @@
|
||||
////
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id='odo-cli-reference']
|
||||
= odo CLI reference
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: odo-cli-reference
|
||||
|
||||
toc::[]
|
||||
|
||||
include::modules/developer-cli-odo-ref-build-images.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-catalog.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-create.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-delete.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-deploy.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-link.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-registry.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-service.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-storage.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-flags.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-ref-json-output.adoc[leveloffset=+1]
|
||||
////
|
||||
@@ -1,20 +0,0 @@
|
||||
////
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="understanding-odo"]
|
||||
= Understanding odo
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: understanding-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
Red Hat OpenShift Developer CLI (`odo`) is a tool for creating applications on {product-title} and Kubernetes. With `{odo-title}`, you can develop, test, debug, and deploy microservices-based applications on a Kubernetes cluster without having a deep understanding of the platform.
|
||||
|
||||
`{odo-title}` follows a _create and push_ workflow. As a user, when you _create_, the information (or manifest) is stored in a configuration file. When you _push_, the corresponding resources are created on the Kubernetes cluster. All of this configuration is stored in the Kubernetes API for seamless accessibility and functionality.
|
||||
|
||||
`{odo-title}` uses _service_ and _link_ commands to link components and services together. `{odo-title}` achieves this by creating and deploying services based on Kubernetes Operators in the cluster. Services can be created using any of the Operators available on the Operator Hub. After linking a service, `odo` injects the service configuration into the component. Your application can then use this configuration to communicate with the Operator-backed service.
|
||||
|
||||
include::modules/odo-key-features.adoc[leveloffset=+1]
|
||||
include::modules/odo-core-concepts.adoc[leveloffset=+1]
|
||||
include::modules/odo-listing-components.adoc[leveloffset=+1]
|
||||
include::modules/odo-telemetry.adoc[leveloffset=+1]
|
||||
////
|
||||
@@ -1,23 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
[id="about-odo-in-a-restricted-environment"]
|
||||
= About {odo-title} in a restricted environment
|
||||
:context: about-odo-in-a-restricted-environment
|
||||
|
||||
toc::[]
|
||||
|
||||
|
||||
To run `{odo-title}` in a disconnected cluster or a cluster provisioned in a restricted environment, you must ensure that a cluster administrator has created a cluster with a mirrored registry.
|
||||
|
||||
|
||||
To start working in a disconnected cluster, you must first xref:../../../cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/pushing-the-odo-init-image-to-the-restricted-cluster-registry.adoc#pushing-the-odo-init-image-to-a-mirror-registry_pushing-the-odo-init-image-to-the-restricted-cluster-registry[push the `odo` init image to the registry of the cluster] and then overwrite the `odo` init image path using the `ODO_BOOTSTRAPPER_IMAGE` environment variable.
|
||||
|
||||
|
||||
After you push the `odo` init image, you must xref:../../../cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/creating-and-deploying-a-component-to-the-disconnected-cluster.adoc#mirroring-a-supported-builder-image_creating-and-deploying-a-component-to-the-disconnected-cluster[mirror a supported builder image] from the registry, xref:../../../cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/creating-and-deploying-a-component-to-the-disconnected-cluster.adoc#overwriting-the-mirror-registry_creating-and-deploying-a-component-to-the-disconnected-cluster[overwrite a mirror registry] and then xref:../../../cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/creating-and-deploying-a-component-to-the-disconnected-cluster.adoc#creating-a-nodejs-application-with-odo_creating-and-deploying-a-component-to-the-disconnected-cluster[create your application]. A builder image is necessary to configure a runtime environment for your application and also contains the build tool needed to build your application, for example npm for Node.js or Maven for Java. A mirror registry contains all the necessary dependencies for your application.
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
ifdef::openshift-enterprise,openshift-webscale[]
|
||||
* xref:../../../disconnected/mirroring/installing-mirroring-installation-images.adoc#installation-about-mirror-registry_installing-mirroring-installation-images[Mirroring images for a disconnected installation]
|
||||
endif::[]
|
||||
* xref:../../../registry/accessing-the-registry.adoc#registry-accessing-directly_accessing-the-registry[Accessing the registry]
|
||||
@@ -1,20 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="creating-and-deploying-a-component-to-the-disconnected-cluster"]
|
||||
= Creating and deploying a component to the disconnected cluster
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-and-deploying-a-component-to-the-disconnected-cluster
|
||||
|
||||
toc::[]
|
||||
|
||||
After you push the `init` image to a cluster with a mirrored registry, you must mirror a supported builder image for your application with the `oc` tool, overwrite the mirror registry using the environment variable, and then create your component.
|
||||
|
||||
== Prerequisites
|
||||
|
||||
* Install `oc` on the client operating system.
|
||||
* xref:../../../cli_reference/developer_cli_odo/installing-odo.adoc#installing-odo-on-linux_installing-odo[Install `{odo-title}`] on the client operating system.
|
||||
* Access to an restricted cluster with a configured {product-registry} or a mirror registry.
|
||||
* xref:../../../cli_reference/developer_cli_odo/using_odo_in_a_restricted_environment/pushing-the-odo-init-image-to-the-restricted-cluster-registry.adoc#pushing-the-odo-init-image-to-a-mirror-registry_pushing-the-odo-init-image-to-the-restricted-cluster-registry[Push the `odo` init image to your cluster registry].
|
||||
|
||||
include::modules/developer-cli-odo-mirroring-a-supported-builder-image.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-overwriting-a-mirror-registry.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-creating-and-deploying-a-nodejs-application-with-odo.adoc[leveloffset=+1]
|
||||
@@ -1,11 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="creating-and-deploying-devfile-components-to-the-disconnected-cluster"]
|
||||
= Creating and deploying devfile components to the disconnected cluster
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-and-deploying-a-component-to-the-disconnected-cluster
|
||||
|
||||
toc::[]
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-nodejs-application-by-using-a-devfile-in-a-disconnected-cluster.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-java-application-by-using-a-devfile-in-a-disconnected-cluster.adoc[leveloffset=+1]
|
||||
@@ -1,18 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="pushing-the-odo-init-image-to-the-restricted-cluster-registry"]
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
= Pushing the {odo-title} init image to the restricted cluster registry
|
||||
:context: pushing-the-odo-init-image-to-the-restricted-cluster-registry
|
||||
|
||||
toc::[]
|
||||
|
||||
Depending on the configuration of your cluster and your operating system you can either push the `odo` init image to a mirror registry or directly to an {product-registry}.
|
||||
|
||||
== Prerequisites
|
||||
|
||||
* Install `oc` on the client operating system.
|
||||
* xref:../../../cli_reference/developer_cli_odo/installing-odo.adoc#installing-odo-on-linux_installing-odo[Install `{odo-title}`] on the client operating system.
|
||||
* Access to a restricted cluster with a configured {product-registry} or a mirror registry.
|
||||
|
||||
include::modules/developer-cli-odo-pushing-the-odo-init-image-to-a-mirror-registry.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-pushing-the-odo-init-image-to-an-internal-registry-directly.adoc[leveloffset=+1]
|
||||
Reference in New Issue
Block a user