mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
remove unused assemblies
This commit is contained in:
Max Bridges
@@ -1,136 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installing-aws-network-customizations"]
|
||||
= Installing a cluster on AWS with network customizations
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-aws-network-customizations
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
Amazon Web Services (AWS) with customized network configuration options. By
|
||||
customizing your network configuration, your cluster can coexist with existing
|
||||
IP address allocations in your environment and integrate with existing MTU and
|
||||
VXLAN configurations.
|
||||
|
||||
You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
== Prerequisites
|
||||
|
||||
* You reviewed details about the xref:../../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update] processes.
|
||||
* You read the documentation on xref:../../../installing/overview/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../../installing/installing_aws/installing-aws-account.adoc#installing-aws-account[configured an AWS account] to host the cluster.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
If you have an AWS profile stored on your computer, it must not use a temporary session token that you generated while using a multi-factor authentication device. The cluster continues to use your current AWS credentials to create AWS resources for the entire life of the cluster, so you must use key-based, long-term credentials. To generate appropriate keys, see link:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html[Managing Access Keys for IAM Users] in the AWS documentation. You can supply the keys when you run the installation program.
|
||||
====
|
||||
* If you use a firewall, you xref:../../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configured it to allow the sites] that your cluster requires access to.
|
||||
|
||||
include::modules/nw-network-config.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../../installing/installing_aws/installation-config-parameters-aws.adoc#installation-config-parameters-aws[Installation configuration parameters for AWS]
|
||||
|
||||
include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]
|
||||
|
||||
include::modules/installation-aws-tested-machine-types.adoc[leveloffset=+2]
|
||||
include::modules/installation-aws-arm-tested-machine-types.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-aws-config-yaml-customizations.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../../installing/installing_aws/installation-config-parameters-aws.adoc#installation-config-parameters-aws[Installation configuration parameters for AWS]
|
||||
|
||||
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
||||
|
||||
[id="installing-aws-manual-modes_{context}"]
|
||||
== Alternatives to storing administrator-level secrets in the kube-system project
|
||||
|
||||
By default, administrator secrets are stored in the `kube-system` project. If you configured the `credentialsMode` parameter in the `install-config.yaml` file to `Manual`, you must use one of the following alternatives:
|
||||
|
||||
* To manage long-term cloud credentials manually, follow the procedure in xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#manually-create-iam_installing-aws-network-customizations[Manually creating long-term credentials].
|
||||
|
||||
* To implement short-term credentials that are managed outside the cluster for individual components, follow the procedures in xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-with-short-term-creds_installing-aws-network-customizations[Configuring an AWS cluster to use short-term credentials].
|
||||
|
||||
//Manually creating long-term credentials
|
||||
include::modules/manually-create-identity-access-management.adoc[leveloffset=+2]
|
||||
|
||||
//Supertask: Configuring an AWS cluster to use short-term credentials
|
||||
[id="installing-aws-with-short-term-creds_{context}"]
|
||||
=== Configuring an AWS cluster to use short-term credentials
|
||||
|
||||
To install a cluster that is configured to use the AWS Security Token Service (STS), you must configure the CCO utility and create the required AWS resources for your cluster.
|
||||
|
||||
//Task part 1: Configuring the Cloud Credential Operator utility
|
||||
include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]
|
||||
|
||||
//Task part 2: Creating the required AWS resources
|
||||
[id="sts-mode-create-aws-resources-ccoctl_{context}"]
|
||||
==== Creating AWS resources with the Cloud Credential Operator utility
|
||||
|
||||
You have the following options when creating AWS resources:
|
||||
|
||||
* You can use the `ccoctl aws create-all` command to create the AWS resources automatically. This is the quickest way to create the resources. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-at-once_installing-aws-network-customizations[Creating AWS resources with a single command].
|
||||
|
||||
* If you need to review the JSON files that the `ccoctl` tool creates before modifying AWS resources, or if the process the `ccoctl` tool uses to create AWS resources automatically does not meet the requirements of your organization, you can create the AWS resources individually. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-individually_installing-aws-network-customizations[Creating AWS resources individually].
|
||||
|
||||
//Task part 2a: Creating the required AWS resources all at once
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+4]
|
||||
|
||||
//Task part 2b: Creating the required AWS resources individually
|
||||
include::modules/cco-ccoctl-creating-individually.adoc[leveloffset=+4]
|
||||
|
||||
//Task part 3: Incorporating the Cloud Credential Operator utility manifests
|
||||
include::modules/cco-ccoctl-install-creating-manifests.adoc[leveloffset=+3]
|
||||
|
||||
// Network Operator specific configuration
|
||||
include::modules/nw-operator-cr.adoc[leveloffset=+1]
|
||||
include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
For more information on using a Network Load Balancer (NLB) on AWS, see xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc#nw-configuring-ingress-cluster-traffic-aws-network-load-balancer_configuring-ingress-cluster-traffic-aws[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
|
||||
====
|
||||
|
||||
include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
|
||||
|
||||
////
|
||||
Hiding until WMCO 10.19.0 GAs
|
||||
[NOTE]
|
||||
====
|
||||
For more information about using Linux and Windows nodes in the same cluster, see ../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
|
||||
====
|
||||
////
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../../web_console/web-console.adoc#web-console[Accessing the web console] for more details about accessing and understanding the {product-title} web console.
|
||||
|
||||
== Next steps
|
||||
|
||||
* xref:../../../installing/validation_and_troubleshooting/validating-an-installation.adoc#validating-an-installation[Validating an installation].
|
||||
* xref:../../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
||||
* If necessary, you can xref:../../../support/remote_health_monitoring/remote-health-reporting.adoc#remote-health-reporting[Remote health reporting].
|
||||
* If necessary, you can xref:../../../post_installation_configuration/changing-cloud-credentials-configuration.adoc#manually-removing-cloud-creds_changing-cloud-credentials-configuration[remove cloud provider credentials].
|
||||
@@ -1,104 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installing-azure-network-customizations"]
|
||||
= Installing a cluster on Azure with network customizations
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-azure-network-customizations
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a cluster with a
|
||||
customized network configuration on infrastructure that the installation program
|
||||
provisions on Microsoft Azure. By customizing your network configuration, your
|
||||
cluster can coexist with existing IP address allocations in your environment and
|
||||
integrate with existing MTU and VXLAN configurations.
|
||||
|
||||
You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../../installing/installing_azure/installation-config-parameters-azure.adoc#installation-config-parameters-azure[Installation configuration parameters for Azure]
|
||||
|
||||
include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]
|
||||
|
||||
include::modules/installation-azure-tested-machine-types.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-azure-arm-tested-machine-types.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-azure-trusted-launch.adoc[leveloffset=+2]
|
||||
include::modules/installation-azure-confidential-vms.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-azure-dedicated-disks.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-azure-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
||||
|
||||
// Network Operator specific configuration
|
||||
include::modules/nw-network-config.adoc[leveloffset=+1]
|
||||
include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
|
||||
include::modules/nw-operator-cr.adoc[leveloffset=+1]
|
||||
include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
|
||||
|
||||
////
|
||||
Hiding until WMCO 10.19.0 GAs
|
||||
[NOTE]
|
||||
====
|
||||
For more information about using Linux and Windows nodes in the same cluster, see ../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
|
||||
====
|
||||
////
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* For more details about Accelerated Networking, see xref:../../../machine_management/creating_machinesets/creating-machineset-azure.adoc#machineset-azure-accelerated-networking_creating-machineset-azure[Accelerated Networking for Microsoft Azure VMs].
|
||||
|
||||
[id="installing-azure-manual-modes_{context}"]
|
||||
== Alternatives to storing administrator-level secrets in the kube-system project
|
||||
|
||||
By default, administrator secrets are stored in the `kube-system` project. If you configured the `credentialsMode` parameter in the `install-config.yaml` file to `Manual`, you must use one of the following alternatives:
|
||||
|
||||
* To manage long-term cloud credentials manually, follow the procedure in xref:../../../installing/installing_azure/ipi/installing-azure-network-customizations.adoc#manually-create-iam_installing-azure-network-customizations[Manually creating long-term credentials].
|
||||
|
||||
* To implement short-term credentials that are managed outside the cluster for individual components, follow the procedures in xref:../../../installing/installing_azure/ipi/installing-azure-network-customizations.adoc#installing-azure-with-short-term-creds_installing-azure-network-customizations[Configuring an Azure cluster to use short-term credentials].
|
||||
|
||||
//Manually creating long-term credentials
|
||||
include::modules/manually-create-identity-access-management.adoc[leveloffset=+2]
|
||||
|
||||
//Supertask: Configuring an Azure cluster to use short-term credentials
|
||||
[id="installing-azure-with-short-term-creds_{context}"]
|
||||
=== Configuring an Azure cluster to use short-term credentials
|
||||
|
||||
To install a cluster that uses {entra-first}, you must configure the Cloud Credential Operator utility and create the required Azure resources for your cluster.
|
||||
|
||||
//Task part 1: Configuring the Cloud Credential Operator utility
|
||||
include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]
|
||||
|
||||
//Task part 2: Creating the required Azure resources
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+3]
|
||||
|
||||
// Additional steps for the Cloud Credential Operator utility (`ccoctl`)
|
||||
include::modules/cco-ccoctl-install-creating-manifests.adoc[leveloffset=+3]
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../../web_console/web-console.adoc#web-console[Accessing the web console] for more details about accessing and understanding the {product-title} web console.
|
||||
|
||||
== Next steps
|
||||
|
||||
* xref:../../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
xref:../../../support/remote_health_monitoring/remote-health-reporting.adoc#remote-health-reporting[Remote health reporting].
|
||||
@@ -1,137 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
[id="installing-gcp-network-customizations"]
|
||||
= Installing a cluster on {gcp-short} with network customizations
|
||||
:context: installing-gcp-network-customizations
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a cluster with a
|
||||
customized network configuration on infrastructure that the installation program
|
||||
provisions on {gcp-first}. By customizing your network
|
||||
configuration, your cluster can coexist with existing IP address allocations in
|
||||
your environment and integrate with existing MTU and VXLAN configurations. To
|
||||
customize the installation, you modify parameters in the `install-config.yaml`
|
||||
file before you install the cluster.
|
||||
|
||||
You must set most of the network configuration parameters during installation,
|
||||
and you can modify only `kubeProxy` configuration parameters in a running
|
||||
cluster.
|
||||
|
||||
== Prerequisites
|
||||
|
||||
* You reviewed details about the xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update] processes.
|
||||
* You read the documentation on xref:../../installing/overview/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../installing/installing_gcp/installing-gcp-account.adoc#installing-gcp-account[configured a {gcp-short} project] to host the cluster.
|
||||
* If you use a firewall, you xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configured it to allow the sites] that your cluster requires access to.
|
||||
|
||||
include::modules/cluster-entitlements.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/ssh-agent-using.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-config-parameters-gcp[Installation configuration parameters for {gcp-short}]
|
||||
|
||||
include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]
|
||||
|
||||
include::modules/installation-gcp-tested-machine-types.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-gcp-tested-machine-types-arm.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-using-gcp-custom-machine-types.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-gcp-enabling-shielded-vms.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-gcp-enabling-confidential-vms.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-configuration-parameters-additional-gcp_installation-config-parameters-gcp[Additional {gcp-first} configuration parameters]
|
||||
|
||||
include::modules/installation-gcp-managing-dns-solution.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-config-parameters-gcp[Installation configuration parameters for {gcp-first}]
|
||||
|
||||
include::modules/installation-gcp-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-enabling-customer-managed-encryption_creating-machineset-gcp[Enabling customer-managed encryption keys for a compute machine set]
|
||||
|
||||
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
||||
|
||||
//Installing the OpenShift CLI by downloading the binary: Moved up to precede `ccoctl` steps, which require the use of `oc`
|
||||
include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
[id="installing-gcp-manual-modes_{context}"]
|
||||
== Alternatives to storing administrator-level secrets in the kube-system project
|
||||
|
||||
By default, administrator secrets are stored in the `kube-system` project. If you configured the `credentialsMode` parameter in the `install-config.yaml` file to `Manual`, you must use one of the following alternatives:
|
||||
|
||||
* To manage long-term cloud credentials manually, follow the procedure in xref:../../installing/installing_gcp/installing-gcp-network-customizations.adoc#manually-create-iam_installing-gcp-network-customizations[Manually creating long-term credentials].
|
||||
|
||||
* To implement short-term credentials that are managed outside the cluster for individual components, follow the procedures in xref:../../installing/installing_gcp/installing-gcp-network-customizations.adoc#installing-gcp-with-short-term-creds_installing-gcp-network-customizations[Configuring a {gcp-short} cluster to use short-term credentials].
|
||||
|
||||
//Manually creating long-term credentials
|
||||
include::modules/manually-create-identity-access-management.adoc[leveloffset=+2]
|
||||
|
||||
//Supertask: Configuring a GCP cluster to use short-term credentials
|
||||
[id="installing-gcp-with-short-term-creds_{context}"]
|
||||
=== Configuring a {gcp-short} cluster to use short-term credentials
|
||||
|
||||
To install a cluster that is configured to use {gcp-short} Workload Identity, you must configure the CCO utility and create the required {gcp-short} resources for your cluster.
|
||||
|
||||
//Task part 1: Configuring the Cloud Credential Operator utility
|
||||
include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]
|
||||
|
||||
//Task part 2: Creating the required GCP resources
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+3]
|
||||
|
||||
//Task part 3: Incorporating the Cloud Credential Operator utility manifests
|
||||
include::modules/cco-ccoctl-install-creating-manifests.adoc[leveloffset=+3]
|
||||
|
||||
// Network Operator specific configuration
|
||||
include::modules/nw-network-config.adoc[leveloffset=+1]
|
||||
include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
|
||||
include::modules/nw-operator-cr.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-gcp-provisioning-dns-records.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-configuration-parameters-additional-gcp_installation-config-parameters-gcp[Additional {gcp-first} configuration parameters]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../web_console/web-console.adoc#web-console[Accessing the web console] for more details about accessing and understanding the {product-title} web console.
|
||||
|
||||
include::modules/cluster-telemetry.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service
|
||||
|
||||
== Next steps
|
||||
|
||||
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
xref:../../support/remote_health_monitoring/remote-health-reporting.adoc#remote-health-reporting[Remote health reporting].
|
||||
Reference in New Issue
Block a user