mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
Merge pull request #25059 from openshift-cherrypick-robot/cherry-pick-25032-to-enterprise-4.6
[enterprise-4.6] fix headers in assemblies
This commit is contained in:
Vikram Goyal
@@ -23,7 +23,7 @@ ifdef::openshift-enterprise,openshift-webscale[]
|
||||
Note that certain options, such as *Pipelines*, *Event Source*, and *Import Virtual Machines*, are displayed only when the xref:../../pipelines/installing-pipelines.adoc#op-installing-pipelines-operator-in-web-console_installing-pipelines[OpenShift Pipelines], xref:../../serverless/installing_serverless/installing-openshift-serverless.adoc#serverless-install-web-console_installing-openshift-serverless[OpenShift Serverless], and xref:../../virt/install/installing-virt-web.adoc#virt-subscribing-to-the-catalog_installing-virt-web[OpenShift Virtualization] Operators are installed, respectively.
|
||||
endif::[]
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
To create applications using the *Developer* perspective ensure that:
|
||||
|
||||
* You have xref:../../web_console/web-console.adoc#web-console[logged in to the web console].
|
||||
|
||||
@@ -6,7 +6,7 @@ toc::[]
|
||||
|
||||
You can edit the configuration and the source code of the application you create using the *Topology* view.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have xref:../../web_console/web-console.adoc#web-console[logged in to the web console] and have switched to the xref:../../web_console/odc-about-developer-perspective.adoc#odc-about-developer-perspective[*Developer* perspective].
|
||||
* You have the appropriate xref:../../authentication/using-rbac.adoc#default-roles_using-rbac[roles and permissions] in a project to create and modify applications in {product-title}.
|
||||
|
||||
@@ -6,7 +6,7 @@ toc::[]
|
||||
|
||||
The *Topology* view in the *Developer* perspective of the web console provides a visual representation of all the applications within a project, their build status, and the components and services associated with them.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
To view your applications in the *Topology* view and interact with them, ensure that:
|
||||
|
||||
* You have xref:../../web_console/web-console.adoc#web-console[logged in to the web console].
|
||||
|
||||
@@ -11,7 +11,7 @@ include::modules/helm-understanding-helm.adoc[leveloffset=+1]
|
||||
You can use the *Developer* perspective in the web console to select and install a chart from the Helm charts listed in the *Developer Catalog*. You can create a Helm release using these charts, upgrade, rollback, and uninstall the release.
|
||||
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have logged in to the web console and have switched to the xref:../../web_console/odc-about-developer-perspective.adoc#odc-about-developer-perspective[*Developer* perspective].
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
The *Monitoring* view in the *Developer* perspective provides options to monitor your project or application metrics, such as CPU, memory, and bandwidth usage, and network related information.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have xref:../web_console/web-console.adoc#web-console-overview[logged in to the web console] and have switched to the xref:../web_console/odc-about-developer-perspective.adoc#odc-about-developer-perspective[*Developer* perspective].
|
||||
* You have xref:../applications/application_life_cycle_management/odc-creating-applications-using-developer-perspective.adoc#odc-creating-applications-using-developer-perspective[created and deployed applications on {product-title}].
|
||||
|
||||
@@ -15,7 +15,7 @@ Even though the cluster is expected to be functional after the restart, the clus
|
||||
|
||||
If your cluster fails to recover, follow the steps to xref:../backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore to a previous cluster state].
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have xref:../backup_and_restore/graceful-cluster-shutdown.adoc#graceful-shutdown-cluster[gracefully shut down your cluster].
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
This document describes the process to gracefully shut down your cluster. You might need to temporarily shut down your cluster for maintenance reasons, or to save on resource costs.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Take an xref:../backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[etcd backup] prior to shutting down the cluster.
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ If the control plane certificates are not valid on the member being replaced, th
|
||||
If a master node is lost and a new one is created, the etcd cluster Operator handles generating the new TLS certificates and adding the node as an etcd member.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Take an xref:../backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[etcd backup] prior to replacing an unhealthy etcd member.
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ to compromise the cluster and therefore should be granted only to users who are
|
||||
trusted with administrative privileges on the cluster.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review how to xref:../builds/securing-builds-by-strategy.adoc#securing-builds-by-strategy[grant custom build permissions].
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ toc::[]
|
||||
|
||||
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
|
||||
== Prerequisites
|
||||
|
||||
* `{odo-title}` is installed.
|
||||
* You have a running cluster. Developers can use link:https://access.redhat.com/documentation/en-us/red_hat_codeready_containers/[CodeReady Containers (CRC)] to deploy a local cluster quickly.
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
With `{odo-title}`, you can create and deploy applications on clusters.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* `{odo-title}` is installed.
|
||||
* You have a running cluster. You can use link:https://access.redhat.com/documentation/en-us/red_hat_codeready_containers/[CodeReady Containers (CRC)] to deploy a local cluster quickly.
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
This example describes how to deploy and connect a database to a front-end application.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* `{odo-title}` is installed.
|
||||
* `oc` client is installed.
|
||||
|
||||
@@ -12,7 +12,7 @@ include::modules/developer-cli-odo-about-devfiles-in-odo.adoc[leveloffset=+1]
|
||||
|
||||
== Creating a Java application by using a devfile
|
||||
|
||||
.Prerequisites
|
||||
== 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_codeready_containers/[Red Hat CodeReady Containers].
|
||||
|
||||
@@ -13,7 +13,7 @@ Operators are a method of packaging, deploying, and managing Kubernetes services
|
||||
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, go to 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
|
||||
== Prerequisites
|
||||
* Install the `oc` CLI and log into 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/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.
|
||||
|
||||
@@ -7,7 +7,7 @@ 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
|
||||
== Prerequisites
|
||||
|
||||
* Install `oc` on the client operating system.
|
||||
* xref:../../../cli_reference/developer_cli_odo/installing-odo.adoc#installing-odo-on-linux[Install `{odo-title}`] on the client operating system.
|
||||
|
||||
@@ -7,7 +7,7 @@ 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 internal registry.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Install `oc` on the client operating system.
|
||||
* xref:../../../cli_reference/developer_cli_odo/installing-odo.adoc#installing-odo-on-linux[Install `{odo-title}`] on the client operating system.
|
||||
|
||||
@@ -14,7 +14,7 @@ access options.
|
||||
[id="dedicated-configuring-aws-access"]
|
||||
== Configuring AWS infrastructure access
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
* An AWS account with IAM permissions.
|
||||
|
||||
[id="dedicated-aws-account-creation"]
|
||||
|
||||
@@ -156,7 +156,7 @@ perform this task. This should be 1-2 sentences maximum.
|
||||
|
||||
If applicable, include any gotchas (things that could trip up the user or cause the task to fail).
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* A bulleted list of pre-requisites that MUST be performed before the user can complete this task.
|
||||
Skip if there isn't any related information.
|
||||
@@ -169,7 +169,7 @@ Skip if there isn't any related information.
|
||||
|
||||
. Step N
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
You can explain any other tasks that MUST be completed after this task. You can
|
||||
skip this if there are none. Do not include xrefs. If the next steps are closely
|
||||
|
||||
@@ -53,7 +53,7 @@ include::modules/installation-preparing-restricted-cluster-to-gather-support-dat
|
||||
|
||||
include::modules/installation-restricted-network-samples.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
//* TODO need to add the registry secret to the machines, which is different
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
To assist in troubleshooting a failed {product-title} installation, you can
|
||||
gather logs from the bootstrap and control plane, or master, machines. You can also get debug information from the installation program.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You attempted to install an {product-title} cluster, and installation failed.
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ include::modules/installation-aws-iam-user.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-aws-regions.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* Install an {product-title} cluster:
|
||||
** xref:../../installing/installing_aws/installing-aws-default.adoc#installing-aws-default[Quickly install a cluster] with default options
|
||||
|
||||
@@ -10,7 +10,7 @@ cluster on infrastructure that the installation program provisions on
|
||||
Amazon Web Services (AWS). To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -58,7 +58,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
Amazon Web Services (AWS) that uses the default configuration options.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -47,7 +47,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -15,7 +15,7 @@ You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -73,7 +73,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a private cluster into an existing VPC on Amazon Web Services (AWS). The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -61,7 +61,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -13,7 +13,7 @@ CloudFormation templates. You can modify the templates to customize your
|
||||
infrastructure or use the information that they contain to create AWS objects
|
||||
according to your company's policies.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -132,7 +132,7 @@ include::modules/installation-create-ingress-dns-records.adoc[leveloffset=+1]
|
||||
include::modules/installation-aws-user-infra-installation.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster into an existing Amazon Virtual Private Cloud (VPC) on Amazon Web Services (AWS). The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -57,7 +57,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -20,7 +20,7 @@ CloudFormation templates. You can modify the templates to customize your
|
||||
infrastructure or use the information that they contain to create AWS objects
|
||||
according to your company's policies.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* xref:../../installing/install_config/installing-restricted-networks-preparations.adoc#installing-restricted-networks-preparations[Create a mirror registry on your mirror host]
|
||||
and obtain the `imageContentSources` data for your version of {product-title}.
|
||||
@@ -147,7 +147,7 @@ include::modules/installation-create-ingress-dns-records.adoc[leveloffset=+1]
|
||||
include::modules/installation-aws-user-infra-installation.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -29,7 +29,7 @@ include::modules/installation-azure-service-principal.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-azure-regions.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* Install an {product-title} cluster on Azure. You can
|
||||
xref:../../installing/installing_azure/installing-azure-customizations.adoc#installing-azure-customizations[install a customized cluster]
|
||||
|
||||
@@ -10,7 +10,7 @@ cluster on infrastructure that the installation program provisions on
|
||||
Microsoft Azure. To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -45,7 +45,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
Microsoft Azure that uses the default configuration options.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -34,7 +34,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -15,7 +15,7 @@ You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -58,7 +58,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a private cluster into an existing Azure Virtual Network (VNet) on Microsoft Azure. The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -47,7 +47,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -14,7 +14,7 @@ link:https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/ove
|
||||
model your own. You can also create the required resources through other
|
||||
methods; the templates are just an example.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a cluster into an existing Azure Virtual Network (VNet) on Microsoft Azure. The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -43,7 +43,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -15,7 +15,7 @@ You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -79,7 +79,7 @@ include::modules/installation-registry-storage-config.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -17,7 +17,7 @@ link:https://access.redhat.com/articles/4207611[guidelines for deploying {produc
|
||||
before you attempt to install an {product-title} cluster in such an environment.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -87,7 +87,7 @@ include::modules/installation-registry-storage-non-production.adoc[leveloffset=+
|
||||
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -17,7 +17,7 @@ link:https://access.redhat.com/articles/4207611[guidelines for deploying {produc
|
||||
before you attempt to install an {product-title} cluster in such an environment.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* xref:../../installing/install_config/installing-restricted-networks-preparations.adoc#installing-restricted-networks-preparations[Create a registry on your mirror host] and obtain the `imageContentSources` data for your version of {product-title}.
|
||||
+
|
||||
@@ -100,7 +100,7 @@ include::modules/installation-registry-storage-non-production.adoc[leveloffset=+
|
||||
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -22,7 +22,7 @@ include::modules/installation-gcp-permissions.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-gcp-regions.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* Install an {product-title} cluster on GCP. You can
|
||||
xref:../../installing/installing_gcp/installing-gcp-customizations.adoc#installing-gcp-customizations[install a customized cluster]
|
||||
|
||||
@@ -10,7 +10,7 @@ cluster on infrastructure that the installation program provisions on
|
||||
Google Cloud Platform (GCP). To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -46,7 +46,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -9,7 +9,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
Google Cloud Platform (GCP) that uses the default configuration options.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -36,7 +36,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -17,7 +17,7 @@ You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -61,7 +61,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a private cluster into an existing VPC on Google Cloud Platform (GCP). The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -49,7 +49,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -14,7 +14,7 @@ completing these steps or to help model your own. You are also free to create
|
||||
the required resources through other methods; the templates are just an
|
||||
example.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -137,7 +137,7 @@ include::modules/installation-creating-gcp-shared-vpc-cluster-wide-firewall-rule
|
||||
|
||||
include::modules/installation-gcp-user-infra-completing.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -14,7 +14,7 @@ completing these steps or to help model your own. You are also free to create
|
||||
the required resources through other methods; the templates are just an
|
||||
example.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -111,7 +111,7 @@ include::modules/installation-gcp-user-infra-adding-ingress.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-gcp-user-infra-completing.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster into an existing Virtual Private Cloud (VPC) on Google Cloud Platform (GCP). The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify
|
||||
parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -43,7 +43,7 @@ include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -20,7 +20,7 @@ completing these steps or to help model your own. You are also free to create
|
||||
the required resources through other methods; the templates are just an
|
||||
example.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* xref:../../installing/install_config/installing-restricted-networks-preparations.adoc#installing-restricted-networks-preparations[Create a mirror registry on your bastion host]
|
||||
and obtain the `imageContentSources` data for your version of {product-title}.
|
||||
@@ -103,7 +103,7 @@ include::modules/installation-gcp-user-infra-adding-ingress.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-gcp-user-infra-completing.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -19,7 +19,7 @@ link:https://access.redhat.com/articles/4207611[guidelines for deploying {produc
|
||||
Restricted network installations are not tested or supported on IBM Z in {product-title} {product-version}.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Provision
|
||||
xref:../../storage/persistent_storage/persistent-storage-nfs.adoc#persistent-storage-nfs[persistent storage using NFS]
|
||||
@@ -76,7 +76,7 @@ include::modules/installation-registry-storage-non-production.adoc[leveloffset=+
|
||||
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a customized cluster on
|
||||
{rh-openstack-first}. To customize the installation, modify parameters in the `install-config.yaml` before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -40,7 +40,7 @@ include::modules/installation-osp-verifying-cluster-status.adoc[leveloffset=+1]
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-configuring-floating-ip.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a customized cluster on
|
||||
{rh-openstack-first} that uses Kuryr SDN. To customize the installation, modify parameters in the `install-config.yaml` before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -46,7 +46,7 @@ include::modules/installation-osp-verifying-cluster-status.adoc[leveloffset=+1]
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-configuring-floating-ip.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
{rh-openstack-first}.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -35,7 +35,7 @@ include::modules/installation-osp-verifying-cluster-status.adoc[leveloffset=+1]
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-configuring-floating-ip.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -11,7 +11,7 @@ In the event of a failure in {product-title} on OpenStack installation, you can
|
||||
|
||||
== View OpenStack instance logs
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* OpenStack CLI tools are installed
|
||||
|
||||
@@ -23,7 +23,7 @@ The console logs appear.
|
||||
|
||||
== SSH access to an instance
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* OpenStack CLI tools are installed
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ In {product-title} version {product-version}, you can install a cluster on
|
||||
|
||||
Using your own infrastructure allows you to integrate your cluster with existing infrastructure and modifications. The process requires more labor on your part than installer-provisioned installations, because you must create all {rh-openstack} resources, like Nova servers, Neutron ports, and security groups. However, Red Hat provides Ansible playbooks to help you in the deployment process.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update] processes.
|
||||
@@ -61,7 +61,7 @@ include::modules/installation-approve-csrs.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-verifying-installation.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-configuring-floating-ip.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -10,7 +10,7 @@ In {product-title} version {product-version}, you can install a cluster on
|
||||
|
||||
Using your own infrastructure allows you to integrate your cluster with existing infrastructure and modifications. The process requires more labor on your part than installer-provisioned installations, because you must create all {rh-openstack} resources, like Nova servers, Neutron ports, and security groups. However, Red Hat provides Ansible playbooks to help you in the deployment process.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update] processes.
|
||||
@@ -55,7 +55,7 @@ include::modules/installation-approve-csrs.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-verifying-installation.adoc[leveloffset=+1]
|
||||
include::modules/installation-osp-configuring-floating-ip.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
You can remove a cluster that you deployed to {rh-openstack-first} on user-provisioned infrastructure.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Have on your machine
|
||||
** A single directory in which you can create files to help you with the removal process
|
||||
|
||||
@@ -27,7 +27,7 @@ For an alternative to installing a customized cluster, see xref:../../installing
|
||||
This installation program is available for Linux and macOS only.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -85,7 +85,7 @@ After the {product-title} cluster initializes, you can perform the following tas
|
||||
* Optional: After deployment, add or replace SSH keys using the Machine Config Operator (MCO) in {product-title}.
|
||||
* Optional: Remove the `kubeadmin` user. Instead, use the authentication provider to create a user with cluster-admin privileges.
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -20,7 +20,7 @@ For an alternative to installing a default cluster, see xref:../../installing/in
|
||||
This installation program is available for Linux and macOS only.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
VMware vSphere infrastructure that you provision in a restricted network.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* xref:../../installing/install_config/installing-restricted-networks-preparations.adoc#installing-restricted-networks-preparations[Create a registry on your mirror host] and obtain the `imageContentSources` data for your version of {product-title}.
|
||||
+
|
||||
@@ -85,7 +85,7 @@ For instructions about configuring registry storage so that it references the co
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on your
|
||||
VMware vSphere instance by using installer-provisioned infrastructure. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Provision
|
||||
xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage]
|
||||
@@ -63,7 +63,7 @@ include::modules/installation-registry-storage-block-recreate-rollout.adoc[level
|
||||
|
||||
For instructions about configuring registry storage so that it references the correct PVC, see xref:../../registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc#configuring-registry-storage-vsphere[Configuring the registry for vSphere].
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -10,7 +10,7 @@ VMware vSphere instance by using installer-provisioned infrastructure with custo
|
||||
|
||||
You must set most of the network configuration parameters during installation, and you can modify only `kubeProxy` configuration parameters in a running cluster.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Provision
|
||||
xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage]
|
||||
@@ -73,7 +73,7 @@ include::modules/installation-registry-storage-block-recreate-rollout.adoc[level
|
||||
|
||||
For instructions about configuring registry storage so that it references the correct PVC, see xref:../../registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc#configuring-registry-storage-vsphere[Configuring the registry for vSphere].
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on your
|
||||
VMware vSphere instance by using installer-provisioned infrastructure.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Provision
|
||||
xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage]
|
||||
@@ -57,7 +57,7 @@ include::modules/installation-registry-storage-block-recreate-rollout.adoc[level
|
||||
|
||||
For instructions about configuring registry storage so that it references the correct PVC, see xref:../../registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc#configuring-registry-storage-vsphere[Configuring the registry for vSphere].
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -16,7 +16,7 @@ and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review details about the
|
||||
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
||||
@@ -76,7 +76,7 @@ For instructions about configuring registry storage so that it references the co
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
VMware vSphere infrastructure that you provision.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Provision
|
||||
xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage]
|
||||
@@ -78,7 +78,7 @@ For instructions about configuring registry storage so that it references the co
|
||||
include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
|
||||
@@ -12,7 +12,7 @@ You can install Jaeger on {product-title} in either of two ways:
|
||||
* If you do not want to install a service mesh, you can use the Jaeger Operator to install the Red Hat build of Jaeger by itself. To install Jaeger without a service mesh, use the following instructions.
|
||||
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
Before you can install {ProductName}, review the installation activities, and ensure that you meet the prerequisites:
|
||||
|
||||
@@ -38,6 +38,6 @@ include::modules/jaeger-install-elasticsearch.adoc[leveloffset=+1]
|
||||
include::modules/jaeger-install.adoc[leveloffset=+1]
|
||||
|
||||
////
|
||||
.Next steps
|
||||
== Next steps
|
||||
* xref:../../jaeger/jaeger_install/rhbj-deploying.adoc#jaeger-deploying[Deploy {ProductName}].
|
||||
////
|
||||
|
||||
@@ -35,7 +35,7 @@ include::modules/cluster-autoscaler-cr.adoc[leveloffset=+2]
|
||||
:FeatureName: ClusterAutoscaler
|
||||
include::modules/deploying-resource.adoc[leveloffset=+2]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* After you configure the ClusterAutoscaler, you must configure at least one
|
||||
MachineAutoscaler.
|
||||
|
||||
@@ -13,7 +13,7 @@ If you need to modify aspects of a MachineSet outside of scaling,
|
||||
see xref:../machine_management/modifying-machineset.adoc#modifying-machineset[Modifying a MachineSet].
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* If you enabled the cluster-wide proxy and scale up workers not included in `networking.machineNetwork[].cidr` from the installation configuration, you must xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[add the workers to the Proxy object's `noProxy` field] to prevent connection issues.
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ include::modules/metering-install-operator.adoc[leveloffset=+1]
|
||||
|
||||
After adding the Metering Operator to your cluster you can install the components of metering by installing the metering stack.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review the xref:../metering/configuring_metering/metering-about-configuring.adoc#metering-about-configuring[configuration options]
|
||||
* Create a MeteringConfig resource. You can begin the following process to generate a default MeteringConfig, then use the examples in the documentation to modify this default file for your specific installation. Review the following topics to create your MeteringConfig resource:
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
You can upgrade metering to {product-version} by updating the Metering Operator subscription.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* The cluster is updated to 4.5.
|
||||
* The xref:../metering/metering-installing-metering.adoc#metering-install-operator_installing-metering[Metering Operator] is installed from OperatorHub.
|
||||
|
||||
@@ -7,7 +7,7 @@ toc::[]
|
||||
|
||||
Use the following example Reports to get started measuring capacity, usage, and utilization in your cluster. These examples showcase the various types of reports metering offers, along with a selection of the predefined queries.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
* xref:../metering/metering-installing-metering.adoc#metering-install-operator_installing-metering[Install Metering]
|
||||
* Review the details about xref:../metering/metering-using-metering#using-metering[writing and viewing reports].
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ include::modules/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* xref:../metering/metering-installing-metering.adoc#metering-install-operator_installing-metering[Install Metering]
|
||||
* Review the details about the available options that can be configured for a xref:../metering/reports/metering-about-reports.adoc#metering-about-reports[Report] and how they function.
|
||||
|
||||
@@ -18,7 +18,7 @@ team and anyone who might be contributing content to it.
|
||||
This guide itself has been written using the format of the modular docs
|
||||
initiative.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have read through and familiarized yourself with the
|
||||
link:https://redhat-documentation.github.io/modular-docs[Red Hat CCS modular docs guide].
|
||||
|
||||
@@ -14,6 +14,6 @@ include::modules/monitoring-configuring-cluster-for-application-monitoring.adoc[
|
||||
include::modules/monitoring-configuring-monitoring-for-an-application.adoc[leveloffset=+1]
|
||||
include::modules/monitoring-exposing-custom-application-metrics-for-horizontal-pod-autoscaling.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* To automatically adjust the number of pods in which the application runs, xref:../monitoring/application-monitoring.adoc#application-monitoring[configure Horizontal Pod Autoscaling for the application.]
|
||||
|
||||
@@ -8,6 +8,6 @@ toc::[]
|
||||
include::modules/monitoring-about-cluster-monitoring.adoc[leveloffset=+1]
|
||||
include::modules/monitoring-stack-components-and-monitored-targets.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
xref:../../monitoring/cluster_monitoring/configuring-the-monitoring-stack.adoc#configuring-the-monitoring-stack[Configure the monitoring stack.]
|
||||
|
||||
@@ -11,7 +11,7 @@ In {product-title} 4, Ansible is not the primary technology to install {product-
|
||||
|
||||
This section explains what configuration is supported, shows how to configure the monitoring stack, and demonstrates several common configuration scenarios.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* The monitoring stack imposes additional resource requirements. Consult the computing resources recommendations in xref:../../scalability_and_performance/scaling-cluster-monitoring-operator.adoc#scaling-cluster-monitoring-operator[Scaling the Cluster Monitoring Operator] and verify that you have sufficient resources.
|
||||
|
||||
@@ -37,7 +37,7 @@ Running cluster monitoring with persistent storage means that your metrics are s
|
||||
See xref:../../scalability_and_performance/optimizing-storage.adoc#recommended-configurable-storage-technology_persistent-storage[Recommended configurable storage technology].
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Dedicate sufficient local persistent storage to ensure that the disk does not become full. How much storage you need depends on the number of pods. For information on system requirements for persistent storage, see xref:../../scalability_and_performance/scaling-cluster-monitoring-operator.adoc#prometheus-database-storage-requirements[Prometheus database storage requirements].
|
||||
* Make sure you have a persistent volume (PV) ready to be claimed by the persistent volume claim (PVC), one PV for each replica. Because Prometheus has two replicas and Alertmanager has three replicas, you need five PVs to support the entire monitoring stack. The PVs should be available from the Local Storage Operator. This does not apply if you enable dynamically provisioned storage.
|
||||
@@ -78,7 +78,7 @@ include::modules/monitoring-listing-acting-alerting-rules.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/monitoring-attaching-additional-labels-to-your-time-series-and-alerts.adoc[leveloffset=+1]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../monitoring/cluster_monitoring/managing-cluster-alerts.adoc#managing-cluster-alerts[Manage cluster alerts.]
|
||||
* Learn about
|
||||
|
||||
@@ -24,6 +24,6 @@ include::modules/technology-preview.adoc[leveloffset=+0]
|
||||
|
||||
See the xref:../../monitoring/monitoring-your-own-services.adoc#monitoring-your-own-services[documentation on monitoring your own services]. It includes details on accessing non-cluster metrics as a developer or a privileged user.
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
xref:../../monitoring/cluster_monitoring/prometheus-alertmanager-and-grafana.adoc#prometheus-alertmanager-and-grafana[Access the Prometheus, Alertmanager, and Grafana.]
|
||||
|
||||
@@ -29,7 +29,7 @@ include::modules/monitoring-changing-alertmanager-configuration.adoc[leveloffset
|
||||
|
||||
* See xref:../../monitoring/cluster_monitoring/configuring-the-monitoring-stack.adoc#configuring-alertmanager[Configuring Alertmanager] for more information on changing Alertmanager configuration.
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
xref:../../monitoring/cluster_monitoring/examining-cluster-metrics.adoc#examining-cluster-metrics[Examine cluster metrics.]
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ You can configure Horizontal Pod Autoscaling (HPA) for an application that expor
|
||||
:FeatureName: Horizontal Pod Autoscaling for an application
|
||||
include::modules/technology-preview.adoc[leveloffset=+0]
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Install the OpenShift Command-line Interface (CLI), commonly known as `oc`.
|
||||
* You must log in to the cluster with a user that has the `cluster-admin` role.
|
||||
|
||||
@@ -9,7 +9,7 @@ As a cluster administrator, you can designate an IP address block that is extern
|
||||
|
||||
This functionality is generally most useful for clusters installed on bare-metal hardware.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Your network infrastructure must route traffic for the external IP addresses to your cluster.
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ The procedures in this section require prerequisites performed by the cluster
|
||||
administrator.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
Before starting the following procedures, the administrator must:
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ The procedures in this section require prerequisites performed by the cluster
|
||||
administrator.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
Before starting the following procedures, the administrator must:
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ The procedures in this section require prerequisites performed by the cluster
|
||||
administrator.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
Before starting the following procedures, the administrator must:
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Production environments can deny direct access to the Internet and instead have
|
||||
The cluster-wide proxy is only supported if you used a user-provisioned infrastructure installation or provide your own networking, such as a virtual private cloud or virual network, for a supported provider.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Review the xref:../installing/install_config/configuring-firewall.adoc#configuring-firewall[sites that your cluster requires access to] and determine whether any of them must bypass the proxy. By default, all cluster egress traffic is proxied, including calls to the cloud provider API for the cloud that hosts your cluster. Add sites to the Proxy object's `spec.noProxy` field to bypass the proxy if necessary.
|
||||
+
|
||||
|
||||
@@ -16,7 +16,7 @@ include::modules/technology-preview.adoc[leveloffset=+0]
|
||||
:FeatureName: Remote Direct Memory Access (RDMA)
|
||||
include::modules/technology-preview.adoc[leveloffset=+0]
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Install the OpenShift Command-line Interface (CLI), commonly known as `oc`.
|
||||
* Log in as a user with `cluster-admin` privileges.
|
||||
|
||||
@@ -16,6 +16,6 @@ include::modules/nw-multus-create-network.adoc[leveloffset=+1]
|
||||
include::modules/nw-multus-bridge-object.adoc[leveloffset=+2]
|
||||
include::modules/nw-multus-ipam-object.adoc[leveloffset=+2]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../networking/multiple_networks/attaching-pod.adoc#attaching-pod[Attach a Pod to an additional network].
|
||||
|
||||
@@ -14,6 +14,6 @@ include::modules/nw-multus-create-network.adoc[leveloffset=+1]
|
||||
include::modules/nw-multus-host-device-object.adoc[leveloffset=+2]
|
||||
include::modules/nw-multus-ipam-object.adoc[leveloffset=+2]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../networking/multiple_networks/attaching-pod.adoc#attaching-pod[Attach a Pod to an additional network].
|
||||
|
||||
@@ -18,6 +18,6 @@ include::modules/nw-multus-create-network.adoc[leveloffset=+1]
|
||||
include::modules/nw-multus-ipvlan-object.adoc[leveloffset=+2]
|
||||
include::modules/nw-multus-ipam-object.adoc[leveloffset=+2]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../networking/multiple_networks/attaching-pod.adoc#attaching-pod[Attach a Pod to an additional network].
|
||||
|
||||
@@ -21,6 +21,6 @@ include::modules/nw-multus-create-network.adoc[leveloffset=+1]
|
||||
include::modules/nw-multus-macvlan-object.adoc[leveloffset=+2]
|
||||
include::modules/nw-multus-ipam-object.adoc[leveloffset=+2]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../networking/multiple_networks/attaching-pod.adoc#attaching-pod[Attach a Pod to an additional network].
|
||||
|
||||
@@ -21,6 +21,6 @@ include::modules/nw-multus-create-network.adoc[leveloffset=+1]
|
||||
include::modules/nw-multus-macvlan-object.adoc[leveloffset=+2]
|
||||
include::modules/nw-multus-ipam-object.adoc[leveloffset=+2]
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
|
||||
* xref:../../networking/multiple_networks/attaching-pod.adoc#attaching-pod[Attach a Pod to an additional network].
|
||||
|
||||
@@ -20,7 +20,7 @@ accessible, accepting network traffic from Pods and services in all other
|
||||
projects. A globally accessible project can access Pods and services in all
|
||||
other projects.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You must have a cluster configured to use the OpenShift SDN Container Network
|
||||
Interface (CNI) plug-in in multitenant isolation mode.
|
||||
|
||||
@@ -20,7 +20,7 @@ xref:../builds/build-strategies.adoc#build-strategy-s2i_build-strategies[Source-
|
||||
The DPDK base image comes preinstalled with DPDK, and with a build tool that can be used to
|
||||
create a target image containing the DPDK libraries and the application provided by the user.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
Before using the S2I tool, ensure that you have the following components installed and configured:
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ The Samples Operator, which operates in the OpenShift namespace, installs and
|
||||
updates the Red Hat Enterprise Linux (RHEL)-based {product-title} imagestreams
|
||||
and {product-title} templates.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
* Deploy an {product-title} cluster.
|
||||
|
||||
//Add any other prereqs that are always valid before you modify the CRD.
|
||||
|
||||
@@ -20,7 +20,7 @@ to your issue. It can also be useful to review your previous steps to ensure
|
||||
that all the steps were executed correctly.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* Basic Ruby and Rails knowledge.
|
||||
* Locally installed version of Ruby 2.0.0+, Rubygems, Bundler.
|
||||
|
||||
@@ -21,7 +21,7 @@ This section uses the `pipelines-tutorial` example to demonstrate the preceding
|
||||
* `apply_manifest` and `update-deployment` Tasks in link:https://github.com/openshift/pipelines-tutorial/tree/release-tech-preview-1[`pipelines-tutorial`] Git repository.
|
||||
|
||||
[discrete]
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have access to an {product-title} cluster.
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
|
||||
// Prerequisites for installing OpenShift Operator
|
||||
[discrete]
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have access to an {product-title} cluster using an account with `cluster-admin` permissions.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ NOTE: The .NET Core runtime is not yet supported by the Pipeline templates.
|
||||
////
|
||||
|
||||
[Discrete]
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You have access to an {product-title} cluster and have switched to the xref:../web_console/odc-about-developer-perspective.adoc[Developer perspective] in the web console.
|
||||
* You have the xref:../pipelines/installing-pipelines.adoc#installing-pipelines[OpenShift Pipelines Operator installed] in your cluster.
|
||||
|
||||
@@ -20,7 +20,7 @@ to the registry using the `oc login` command. The operations you can perform
|
||||
depend on your user permissions, as described in the following sections.
|
||||
|
||||
ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You must have configured an identity provider (IDP).
|
||||
* For pulling images, for example when using the `podman pull` command,
|
||||
|
||||
@@ -16,7 +16,7 @@ xref:../../serverless/knative_eventing/serverless-sinkbinding.adoc#serverless-si
|
||||
|
||||
You can create and manage Knative event sources using the **Developer** perspective in the {product-title} web console, the `kn` CLI, or by applying YAML files.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You must have a current installation of xref:../../serverless/installing_serverless/installing-openshift-serverless.adoc#serverless-install-web-console_installing-openshift-serverless[{ServerlessProductName}], including Knative Serving and Eventing, in your {product-title} cluster. This can be installed by a cluster administrator.
|
||||
* Event sources need a service to use as an event _sink_. The sink is the service or application that events are sent to from the event source.
|
||||
|
||||
@@ -9,7 +9,7 @@ toc::[]
|
||||
ApiServerSource is an event source that can be used to connect an event sink, such as a Knative service, to the Kubernetes API server.
|
||||
ApiServerSource watches for Kubernetes events and forwards them to the Knative Eventing broker.
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
|
||||
* You must have a current installation of xref:../../serverless/installing_serverless/installing-openshift-serverless.adoc#serverless-install-web-console_installing-openshift-serverless[{ServerlessProductName}], including Knative Serving and Eventing, in your {product-title} cluster. This can be installed by a cluster administrator.
|
||||
* Event sources need a service to use as an event _sink_. The sink is the service or application that events are sent to from the event source.
|
||||
|
||||
@@ -37,6 +37,6 @@ Service 'event-display' created to latest revision 'event-display-sjptv-1' is av
|
||||
http://event-display-knative-serving.apps.ci-ln-kf2fv0k-d5d6b.origin-ci-int-aws.dev.rhcloud.com
|
||||
////
|
||||
|
||||
.Next steps
|
||||
== Next steps
|
||||
* See the documentation on xref:../serverless-apiserversource.adoc#serverless-apiserversource[Using ApiServerSource].
|
||||
* See the documentation on xref:../serverless-pingsource.adoc#serverless-pingsource[Using PingSource].
|
||||
|
||||
@@ -18,7 +18,7 @@ This guide provides information about installing Knative Eventing using the defa
|
||||
|
||||
include::modules/serverless-create-eventing-namespace.adoc[leveloffset=+1]
|
||||
|
||||
.Prerequisites
|
||||
== Prerequisites
|
||||
* An {product-title} account with cluster administrator access
|
||||
* Installed {ServerlessOperatorName}
|
||||
* Created the `knative-eventing` namespace
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user