mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Removing Alibaba references from IPI
This commit is contained in:
Shubha Narayanan
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
f77f2f5476
commit
fad72d1032
@@ -134,24 +134,10 @@ Topics:
|
||||
File: installing-mirroring-disconnected
|
||||
- Name: Mirroring images for a disconnected installation using oc-mirror V2
|
||||
File: about-installing-oc-mirror-v2
|
||||
- Name: Installing on Alibaba
|
||||
- Name: Installing on Alibaba Cloud by using Assisted Installer
|
||||
Dir: installing_alibaba
|
||||
Distros: openshift-origin,openshift-enterprise
|
||||
Topics:
|
||||
- Name: Preparing to install on Alibaba Cloud
|
||||
File: preparing-to-install-on-alibaba
|
||||
- Name: Creating the required Alibaba Cloud resources
|
||||
File: manually-creating-alibaba-ram
|
||||
- Name: Installing a cluster quickly on Alibaba Cloud
|
||||
File: installing-alibaba-default
|
||||
- Name: Installing a cluster on Alibaba Cloud with customizations
|
||||
File: installing-alibaba-customizations
|
||||
- Name: Installing a cluster on Alibaba Cloud with network customizations
|
||||
File: installing-alibaba-network-customizations
|
||||
- Name: Installing a cluster on Alibaba Cloud into an existing VPC
|
||||
File: installing-alibaba-vpc
|
||||
- Name: Installation configuration parameters for Alibaba Cloud
|
||||
File: installation-config-parameters-alibaba
|
||||
- Name: Uninstalling a cluster on Alibaba Cloud
|
||||
File: uninstall-cluster-alibaba
|
||||
- Name: Installing on AWS
|
||||
|
||||
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
Manual mode is supported for Alibaba Cloud, Amazon Web Services (AWS), global Microsoft Azure, Microsoft Azure Stack Hub, Google Cloud Platform (GCP), {ibm-cloud-name}, and Nutanix.
|
||||
Manual mode is supported for Amazon Web Services (AWS), global Microsoft Azure, Microsoft Azure Stack Hub, Google Cloud Platform (GCP), {ibm-cloud-name}, and Nutanix.
|
||||
|
||||
[id="manual-mode-classic_{context}"]
|
||||
== User-managed credentials
|
||||
@@ -26,7 +26,6 @@ An AWS, global Azure, or GCP cluster that uses manual mode might be configured t
|
||||
[id="additional-resources_cco-mode-manual"]
|
||||
== Additional resources
|
||||
|
||||
* xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[Manually creating RAM resources for Alibaba Cloud]
|
||||
* xref:../../installing/installing_aws/ipi/installing-aws-customizations.adoc#manually-create-iam_installing-aws-customizations[Manually creating long-term credentials for AWS]
|
||||
* xref:../../installing/installing_azure/installing-azure-customizations.adoc#manually-create-iam_installing-azure-customizations[Manually creating long-term credentials for Azure]
|
||||
* xref:../../installing/installing_gcp/installing-gcp-customizations.adoc#manually-create-iam_installing-gcp-customizations[Manually creating long-term credentials for GCP]
|
||||
|
||||
@@ -87,7 +87,6 @@ To enable FIPS mode for your cluster, you must run the installation program from
|
||||
====
|
||||
|
||||
* xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[Amazon Web Services]
|
||||
* xref:../installing/installing_alibaba/installing-alibaba-customizations.adoc#installing-alibaba-customizations[Alibaba Cloud]
|
||||
* xref:../installing/installing_azure/installing-azure-customizations.adoc#installing-azure-customizations[Microsoft Azure]
|
||||
* xref:../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Bare metal]
|
||||
* xref:../installing/installing_gcp/installing-gcp-customizations.adoc#installing-gcp-customizations[Google Cloud Platform]
|
||||
|
||||
@@ -17,7 +17,6 @@ Before you install an {product-title} cluster, you need to select the best insta
|
||||
|
||||
If you want to install and manage {product-title} yourself, you can install it on the following platforms:
|
||||
|
||||
* Alibaba Cloud
|
||||
* Amazon Web Services (AWS) on 64-bit x86 instances
|
||||
ifndef::openshift-origin[]
|
||||
* Amazon Web Services (AWS) on 64-bit ARM instances
|
||||
@@ -54,9 +53,9 @@ Because you need to provision machines as part of the {product-title} cluster in
|
||||
|
||||
Because the operating system is integral to {product-title}, it is easier to let the installation program for {product-title} stand up all of the infrastructure. These are called _installer provisioned infrastructure_ installations. In this type of installation, you can provide some existing infrastructure to the cluster, but the installation program deploys all of the machines that your cluster initially needs.
|
||||
|
||||
You can deploy an installer-provisioned infrastructure cluster without specifying any customizations to the cluster or its underlying machines to xref:../installing/installing_alibaba/installing-alibaba-default.adoc#installing-alibaba-default[Alibaba Cloud], xref:../installing/installing_aws/ipi/installing-aws-default.adoc#installing-aws-default[AWS], xref:../installing/installing_azure/installing-azure-default.adoc#installing-azure-default[Azure], xref:../installing/installing_azure_stack_hub/installing-azure-stack-hub-default.adoc#installing-azure-stack-hub-default[Azure Stack Hub], xref:../installing/installing_gcp/installing-gcp-default.adoc#installing-gcp-default[GCP], xref:../installing/installing_nutanix/installing-nutanix-installer-provisioned.adoc#installing-nutanix-installer-provisioned[Nutanix].
|
||||
You can deploy an installer-provisioned infrastructure cluster without specifying any customizations to the cluster or its underlying machines to xref:../installing/installing_aws/ipi/installing-aws-default.adoc#installing-aws-default[AWS], xref:../installing/installing_azure/installing-azure-default.adoc#installing-azure-default[Azure], xref:../installing/installing_azure_stack_hub/installing-azure-stack-hub-default.adoc#installing-azure-stack-hub-default[Azure Stack Hub], xref:../installing/installing_gcp/installing-gcp-default.adoc#installing-gcp-default[GCP], xref:../installing/installing_nutanix/installing-nutanix-installer-provisioned.adoc#installing-nutanix-installer-provisioned[Nutanix].
|
||||
|
||||
If you need to perform basic configuration for your installer-provisioned infrastructure cluster, such as the instance type for the cluster machines, you can customize an installation for xref:../installing/installing_alibaba/installing-alibaba-customizations.adoc#installing-alibaba-customizations[Alibaba Cloud], xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[AWS], xref:../installing/installing_azure/installing-azure-customizations.adoc#installing-azure-customizations[Azure], xref:../installing/installing_gcp/installing-gcp-customizations.adoc#installing-gcp-customizations[GCP], xref:../installing/installing_nutanix/installing-nutanix-installer-provisioned.adoc#installing-nutanix-installer-provisioned[Nutanix].
|
||||
If you need to perform basic configuration for your installer-provisioned infrastructure cluster, such as the instance type for the cluster machines, you can customize an installation for xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[AWS], xref:../installing/installing_azure/installing-azure-customizations.adoc#installing-azure-customizations[Azure], xref:../installing/installing_gcp/installing-gcp-customizations.adoc#installing-gcp-customizations[GCP], xref:../installing/installing_nutanix/installing-nutanix-installer-provisioned.adoc#installing-nutanix-installer-provisioned[Nutanix].
|
||||
|
||||
For installer-provisioned infrastructure installations, you can use an existing xref:../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[VPC in AWS], xref:../installing/installing_azure/installing-azure-vnet.adoc#installing-azure-vnet[vNet in Azure], or xref:../installing/installing_gcp/installing-gcp-vpc.adoc#installing-gcp-vpc[VPC in GCP]. You can also reuse part of your networking infrastructure so that your cluster in xref:../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[AWS], xref:../installing/installing_azure/installing-azure-network-customizations.adoc#installing-azure-network-customizations[Azure], xref:../installing/installing_gcp/installing-gcp-network-customizations.adoc#installing-gcp-network-customizations[GCP] can coexist with existing IP address allocations in your environment and integrate with existing MTU and VXLAN configurations. If you have existing accounts and credentials on these clouds, you can re-use them, but you might need to modify the accounts to have the required permissions to install {product-title} clusters on them.
|
||||
|
||||
@@ -131,10 +130,9 @@ Not all installation options are supported for all platforms, as shown in the fo
|
||||
//This table is for all flavors of OpenShift, except OKD. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifndef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS (64-bit x86) |AWS (64-bit ARM) |Azure (64-bit x86) |Azure (64-bit ARM)|Azure Stack Hub |GCP (64-bit x86) |GCP (64-bit ARM) |Nutanix |{rh-openstack} |Bare metal (64-bit x86) |Bare metal (64-bit ARM) |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-power-name} |{ibm-power-server-name}
|
||||
||AWS (64-bit x86) |AWS (64-bit ARM) |Azure (64-bit x86) |Azure (64-bit ARM)|Azure Stack Hub |GCP (64-bit x86) |GCP (64-bit ARM) |Nutanix |{rh-openstack} |Bare metal (64-bit x86) |Bare metal (64-bit ARM) |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-power-name} |{ibm-power-server-name}
|
||||
|
||||
|Default
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-default.adoc#installing-alibaba-default[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-default.adoc#installing-aws-default[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-default.adoc#installing-aws-default[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-default.adoc#installing-azure-default[✓]
|
||||
@@ -153,7 +151,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Custom
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-customizations.adoc#installing-alibaba-customizations[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-customizations.adoc#installing-azure-customizations[✓]
|
||||
@@ -173,7 +170,6 @@ ifndef::openshift-origin[]
|
||||
|
||||
|
||||
|Network customization
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-network-customizations.adoc#installing-alibaba-network-customizations[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-network-customizations.adoc#installing-azure-network-customizations[✓]
|
||||
@@ -192,7 +188,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Restricted network
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-restricted-networks-aws-installer-provisioned.adoc#installing-restricted-networks-aws-installer-provisioned[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-restricted-networks-aws-installer-provisioned.adoc#installing-restricted-networks-aws-installer-provisioned[✓]
|
||||
|xref:../installing/installing_azure/installing-restricted-networks-azure-installer-provisioned.adoc#installing-restricted-networks-azure-installer-provisioned[✓]
|
||||
@@ -211,7 +206,6 @@ ifndef::openshift-origin[]
|
||||
|xref:../installing/installing_ibm_powervs/installing-restricted-networks-ibm-power-vs.adoc#installing-restricted-networks-ibm-power-vs[✓]
|
||||
|
||||
|Private clusters
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-private.adoc#installing-aws-private[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-private.adoc#installing-aws-private[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-private.adoc#installing-azure-private[✓]
|
||||
@@ -230,7 +224,6 @@ ifndef::openshift-origin[]
|
||||
|xref:../installing/installing_ibm_powervs/installing-ibm-power-vs-private-cluster.adoc#installing-ibm-power-vs-private-cluster[✓]
|
||||
|
||||
|Existing virtual private networks
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-vnet.adoc#installing-azure-vnet[✓]
|
||||
@@ -249,7 +242,6 @@ ifndef::openshift-origin[]
|
||||
|xref:../installing/installing_ibm_powervs/installing-ibm-powervs-vpc.adoc#installing-ibm-powervs-vpc[✓]
|
||||
|
||||
|Government regions
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-government-region.adoc#installing-aws-government-region[✓]
|
||||
|
|
||||
|xref:../installing/installing_azure/installing-azure-government-region.adoc#installing-azure-government-region[✓]
|
||||
@@ -268,7 +260,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Secret regions
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-secret-region.adoc#installing-aws-secret-region[✓]
|
||||
|
|
||||
|
|
||||
@@ -287,7 +278,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
||||
|China regions
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-china.adoc#installing-aws-china-region[✓]
|
||||
|
|
||||
|
|
||||
@@ -310,11 +300,10 @@ endif::openshift-origin[]
|
||||
//This table is for OKD only. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifdef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |Bare metal |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-power-name}
|
||||
||AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |Bare metal |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-power-name}
|
||||
|
||||
|
||||
|Default
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-default.adoc#installing-alibaba-default[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-default.adoc#installing-aws-default[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-default.adoc#installing-azure-default[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-default.adoc#installing-azure-default[✓]
|
||||
@@ -328,7 +317,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Custom
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-customizations.adoc#installing-alibaba-customizations[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-customizations.adoc#installing-azure-customizations[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-default.adoc#installing-azure-default[✓]
|
||||
@@ -342,7 +330,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Network customization
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-network-customizations.adoc#installing-alibaba-network-customizations[✓]
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-network-customizations.adoc#installing-azure-network-customizations[✓]
|
||||
|xref:../installing/installing_azure_stack_hub/installing-azure-stack-hub-network-customizations.adoc#installing-azure-stack-hub-network-customizations[✓]
|
||||
@@ -356,7 +343,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Restricted network
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-restricted-networks-aws-installer-provisioned.adoc#installing-restricted-networks-aws-installer-provisioned[✓]
|
||||
|
|
||||
|
|
||||
@@ -370,7 +356,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Private clusters
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-private.adoc#installing-aws-private[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-private.adoc#installing-azure-private[✓]
|
||||
|
|
||||
@@ -384,7 +369,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Existing virtual private networks
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-vnet.adoc#installing-azure-vnet[✓]
|
||||
|
|
||||
@@ -398,7 +382,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Government regions
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-government-region.adoc#installing-aws-government-region[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-government-region.adoc#installing-azure-government-region[✓]
|
||||
|
|
||||
@@ -412,7 +395,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Secret regions
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-secret-region.adoc#installing-aws-secret-region[✓]
|
||||
|
|
||||
|
|
||||
@@ -426,7 +408,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|China regions
|
||||
|
|
||||
|xref:../installing/installing_aws/ipi/installing-aws-china.adoc#installing-aws-china-region[✓]
|
||||
|
|
||||
|
|
||||
@@ -445,11 +426,10 @@ endif::openshift-origin[]
|
||||
//This table is for all flavors of OpenShift, except OKD. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifndef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS (64-bit x86) |AWS (64-bit ARM) |Azure (64-bit x86) |Azure (64-bit ARM) |Azure Stack Hub |GCP (64-bit x86) |GCP (64-bit ARM) |Nutanix |{rh-openstack} |Bare metal (64-bit x86) |Bare metal (64-bit ARM) |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-z-name} with {op-system-base} KVM |{ibm-power-name} |Platform agnostic
|
||||
||AWS (64-bit x86) |AWS (64-bit ARM) |Azure (64-bit x86) |Azure (64-bit ARM) |Azure Stack Hub |GCP (64-bit x86) |GCP (64-bit ARM) |Nutanix |{rh-openstack} |Bare metal (64-bit x86) |Bare metal (64-bit ARM) |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-z-name} with {op-system-base} KVM |{ibm-power-name} |Platform agnostic
|
||||
|
||||
|
||||
|Custom
|
||||
|
|
||||
|xref:../installing/installing_aws/upi/installing-aws-user-infra.adoc#installing-aws-user-infra[✓]
|
||||
|xref:../installing/installing_aws/upi/installing-aws-user-infra.adoc#installing-aws-user-infra[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-user-infra.adoc#installing-azure-user-infra[✓]
|
||||
@@ -479,7 +459,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|xref:../installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc#installing-bare-metal-network-customizations[✓]
|
||||
|xref:../installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc#installing-bare-metal-network-customizations[✓]
|
||||
|xref:../installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc#installing-vsphere-network-customizations[✓]
|
||||
@@ -490,7 +469,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Restricted network
|
||||
|
|
||||
|xref:../installing/installing_aws/upi/installing-restricted-networks-aws.adoc#installing-restricted-networks-aws[✓]
|
||||
|xref:../installing/installing_aws/upi/installing-restricted-networks-aws.adoc#installing-restricted-networks-aws[✓]
|
||||
|
|
||||
@@ -515,7 +493,6 @@ ifndef::openshift-origin[]
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|xref:../installing/installing_gcp/installing-gcp-user-infra-vpc.adoc#installing-gcp-user-infra-vpc[✓]
|
||||
|xref:../installing/installing_gcp/installing-gcp-user-infra-vpc.adoc#installing-gcp-user-infra-vpc[✓]
|
||||
|
|
||||
@@ -535,11 +512,10 @@ endif::openshift-origin[]
|
||||
//This table is for OKD only. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifdef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack}|Bare metal |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-z-name} with {op-system-base} KVM |{ibm-power-name} |Platform agnostic
|
||||
||AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack}|Bare metal |vSphere |{ibm-cloud-name} |{ibm-z-name} |{ibm-z-name} with {op-system-base} KVM |{ibm-power-name} |Platform agnostic
|
||||
|
||||
|
||||
|Custom
|
||||
|
|
||||
|xref:../installing/installing_aws/upi/installing-aws-user-infra.adoc#installing-aws-user-infra[✓]
|
||||
|xref:../installing/installing_azure/installing-azure-user-infra.adoc#installing-azure-user-infra[✓]
|
||||
|xref:../installing/installing_azure_stack_hub/installing-azure-stack-hub-user-infra.adoc#installing-azure-stack-hub-user-infra[✓]
|
||||
@@ -562,7 +538,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|xref:../installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc#installing-bare-metal-network-customizations[✓]
|
||||
|xref:../installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc#installing-vsphere-network-customizations[✓]
|
||||
|
|
||||
@@ -572,7 +547,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
||||
|Restricted network
|
||||
|
|
||||
|xref:../installing/installing_aws/upi/installing-restricted-networks-aws.adoc#installing-restricted-networks-aws[✓]
|
||||
|
|
||||
|
|
||||
@@ -591,7 +565,6 @@ ifdef::openshift-origin[]
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|xref:../installing/installing_gcp/installing-gcp-user-infra-vpc.adoc#installing-gcp-user-infra-vpc[✓]
|
||||
|
|
||||
|
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installation-config-parameters-alibaba"]
|
||||
= Installation configuration parameters for Alibaba Cloud
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installation-config-parameters-alibaba
|
||||
:platform: Alibaba Cloud
|
||||
|
||||
toc::[]
|
||||
|
||||
Before you deploy an {product-title} cluster on Alibaba Cloud, you provide parameters to customize your cluster and the platform that hosts it. When you create the `install-config.yaml` file, you provide values for the required parameters through the command line. You can then modify the `install-config.yaml` file to customize your cluster further.
|
||||
|
||||
include::modules/installation-configuration-parameters.adoc[leveloffset=+1]
|
||||
@@ -1,72 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installing-alibaba-customizations"]
|
||||
= Installing a cluster on Alibaba Cloud with customizations
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-alibaba-customizations
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a customized cluster on infrastructure that the installation program provisions on Alibaba Cloud. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The scope of the {product-title} installation configurations is intentionally narrow. It is designed for simplicity and ensured success. You can complete many more {product-title} configuration tasks after an installation completes.
|
||||
====
|
||||
|
||||
:FeatureName: Alibaba Cloud on {product-title}
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
[id="prerequisites_installing-alibaba-customizations"]
|
||||
== 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/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../installing/installing_alibaba/preparing-to-install-on-alibaba.adoc#installation-alibaba-dns_preparing-to-install-on-alibaba[registered your domain].
|
||||
* 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.
|
||||
* If the cloud Resource Access Management (RAM) APIs are not accessible in your environment, or if you do not want to store an administrator-level credential secret in the `kube-system` namespace, you can xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[manually create and maintain Resource Access Management (RAM) credentials].
|
||||
|
||||
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=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_alibaba/installation-config-parameters-alibaba.adoc#installation-config-parameters-alibaba[Installation configuration parameters for Alibaba Cloud]
|
||||
|
||||
include::modules/manually-creating-alibaba-manifests.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-alibaba-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
|
||||
|
||||
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.
|
||||
* 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
|
||||
* 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.
|
||||
|
||||
[id="next-steps_installing-alibaba-customizations"]
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/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/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
||||
//Given that manual mode is required to install on Alibaba Cloud, I do not believe this xref is necessary.
|
||||
//* 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,60 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installing-alibaba-default"]
|
||||
= Installing a cluster quickly on Alibaba Cloud
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-alibaba-default
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
Alibaba Cloud that uses the default configuration options.
|
||||
|
||||
:FeatureName: Alibaba Cloud on {product-title}
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
[id="prerequisites_installing-alibaba-default"]
|
||||
== 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/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../installing/installing_alibaba/preparing-to-install-on-alibaba.adoc#installation-alibaba-dns_preparing-to-install-on-alibaba[registered your domain].
|
||||
* 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.
|
||||
* You have xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[created the required Alibaba Cloud resources].
|
||||
* If the cloud Resource Access Management (RAM) APIs are not accessible in your environment, or if you do not want to store an administrator-level credential secret in the kube-system namespace, you can xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[manually create and maintain Resource Access Management (RAM) credentials].
|
||||
|
||||
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]
|
||||
|
||||
include::modules/manually-creating-alibaba-manifests.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cluster-telemetry.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.
|
||||
* 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
|
||||
|
||||
[id="next-steps_installing-alibaba-default"]
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/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/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
||||
//Given that manual mode is required to install on Alibaba Cloud, I do not believe this xref is necessary.
|
||||
//* 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,82 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installing-alibaba-network-customizations"]
|
||||
= Installing a cluster on Alibaba Cloud with network customizations
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-alibaba-network-customizations
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} {product-version}, you can install a cluster on Alibaba Cloud 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.
|
||||
|
||||
:FeatureName: Alibaba Cloud on {product-title}
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
[id="prerequisites_installing-alibaba-network-customizations"]
|
||||
== 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/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../installing/installing_alibaba/preparing-to-install-on-alibaba.adoc#installation-alibaba-dns_preparing-to-install-on-alibaba[registered your domain].
|
||||
* 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.
|
||||
* If the cloud Resource Access Management (RAM) APIs are not accessible in your environment, or if you do not want to store an administrator-level credential secret in the `kube-system` namespace, you can xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[manually create and maintain Resource Access Management (RAM) credentials].
|
||||
|
||||
include::modules/cluster-entitlements.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/ssh-agent-using.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
|
||||
|
||||
//Networking-specific customization module
|
||||
include::modules/nw-network-config.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_alibaba/installation-config-parameters-alibaba.adoc#installation-config-parameters-alibaba[Installation configuration parameters for Alibaba Cloud]
|
||||
|
||||
include::modules/manually-creating-alibaba-manifests.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-alibaba-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
||||
|
||||
//Networking-specific customization module
|
||||
include::modules/nw-operator-cr.adoc[leveloffset=+1]
|
||||
|
||||
//Networking-specific customization module
|
||||
include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
|
||||
|
||||
//Networking-specific customization module
|
||||
include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
|
||||
|
||||
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.
|
||||
* 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
|
||||
* 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.
|
||||
|
||||
[id="next-steps_installing-alibaba-network-customizations"]
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/validating-an-installation.adoc#validating-an-installation[Validate an installation].
|
||||
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
||||
* If necessary, you can xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
||||
//Given that manual mode is required to install on Alibaba Cloud, I do not believe this xref is necessary.
|
||||
//* 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,73 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="installing-alibaba-vpc"]
|
||||
= Installing a cluster on Alibaba Cloud into an existing VPC
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-alibaba-vpc
|
||||
|
||||
toc::[]
|
||||
|
||||
In {product-title} version {product-version}, you can install a cluster into an existing Alibaba Virtual Private Cloud (VPC) on Alibaba Cloud Services. The installation program provisions the required infrastructure, which can then be customized. To customize the VPC installation, modify the parameters in the 'install-config.yaml' file before you install the cluster.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The scope of the {product-title} installation configurations is intentionally narrow. It is designed for simplicity and ensured success. You can complete many more {product-title} configuration tasks after an installation completes.
|
||||
====
|
||||
|
||||
:FeatureName: Alibaba Cloud on {product-title}
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
[id="prerequisites_installing-alibaba-vpc"]
|
||||
== 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/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../installing/installing_alibaba/preparing-to-install-on-alibaba.adoc#installation-alibaba-dns_preparing-to-install-on-alibaba[registered your domain].
|
||||
* 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.
|
||||
* If the cloud Resource Access Management (RAM) APIs are not accessible in your environment, or if you do not want to store an administrator-level credential secret in the `kube-system` namespace, you can xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[manually create and maintain Resource Access Management (RAM) credentials].
|
||||
|
||||
include::modules/installation-custom-alibaba-vpc.adoc[leveloffset=+1]
|
||||
|
||||
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=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../installing/installing_alibaba/installation-config-parameters-alibaba.adoc#installation-config-parameters-alibaba[Installation configuration parameters for Alibaba Cloud]
|
||||
|
||||
include::modules/installation-alibaba-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/manually-creating-alibaba-manifests.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/cco-ccoctl-configuring.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+2]
|
||||
|
||||
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-installing-cli.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
|
||||
|
||||
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.
|
||||
* 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
|
||||
|
||||
[id="next-steps_installing-alibaba-vpc"]
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/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/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
||||
//Given that manual mode is required to install on Alibaba Cloud, I do not believe this xref is necessary.
|
||||
//* 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,34 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="manually-creating-alibaba-ram"]
|
||||
= Creating the required Alibaba Cloud resources
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: manually-creating-alibaba-ram
|
||||
|
||||
toc::[]
|
||||
|
||||
Before you install {product-title}, you must use the Alibaba Cloud console to create a Resource Access Management (RAM) user that has sufficient permissions to install {product-title} into your Alibaba Cloud. This user must also have permissions to create new RAM users. You can also configure and use the `ccoctl` tool to create new credentials for the {product-title} components with the permissions that they require.
|
||||
|
||||
:FeatureName: Alibaba Cloud on {product-title}
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
//Task part 1: Manually creating the required RAM user
|
||||
include::modules/manually-creating-alibaba-ram-user.adoc[leveloffset=+1]
|
||||
|
||||
//Task part 2: Configuring the Cloud Credential Operator utility
|
||||
include::modules/cco-ccoctl-configuring.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../updating/preparing_for_updates/preparing-manual-creds-update.adoc#preparing-manual-creds-update[Preparing to update a cluster with manually maintained credentials]
|
||||
|
||||
//Task part 3: Creating Alibaba resources with a single command
|
||||
// modules/cco-ccoctl-creating-at-once.adoc[leveloffset=+1]
|
||||
|
||||
[id="next-steps_manually-creating-alibaba-ram"]
|
||||
== Next steps
|
||||
|
||||
* Install a cluster on Alibaba Cloud infrastructure that is provisioned by the {product-title} installation program, by using one of the following methods:
|
||||
|
||||
** **xref:../../installing/installing_alibaba/installing-alibaba-default.adoc#installing-alibaba-default[Installing a cluster quickly on Alibaba Cloud]**: You can install a cluster quickly by using the default configuration options.
|
||||
|
||||
** **xref:../../installing/installing_alibaba/installing-alibaba-customizations.adoc#installing-alibaba-customizations[Installing a customized cluster on Alibaba Cloud]**: The installation program allows for some customization to be applied at the installation stage. Many other customization options are available xref:../../post_installation_configuration/cluster-tasks.adoc#post-install-cluster-tasks[post-installation].
|
||||
|
||||
@@ -1,35 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="preparing-to-install-on-alibaba"]
|
||||
= Preparing to install on Alibaba Cloud
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: preparing-to-install-on-alibaba
|
||||
|
||||
toc::[]
|
||||
|
||||
:FeatureName: Alibaba Cloud on {product-title}
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
[id="prerequisites_preparing-to-install-on-alibaba"]
|
||||
== 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/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
|
||||
[id="requirements-for-installing-ocp-on-alibaba"]
|
||||
== Requirements for installing {product-title} on Alibaba Cloud
|
||||
|
||||
Before installing {product-title} on Alibaba Cloud, you must configure and register your domain, create a Resource Access Management (RAM) user for the installation, and review the supported Alibaba Cloud data center regions and zones for the installation.
|
||||
|
||||
include::modules/installation-alibaba-dns.adoc[leveloffset=+1]
|
||||
|
||||
// include modules/installation-alibaba-limits.adoc[leveloffset=+1]
|
||||
|
||||
// include modules/installation-alibaba-ram-user.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/installation-alibaba-regions.adoc[leveloffset=+1]
|
||||
|
||||
[id="next-steps_preparing-to-install-on-alibaba"]
|
||||
== Next steps
|
||||
|
||||
* xref:../../installing/installing_alibaba/manually-creating-alibaba-ram.adoc#manually-creating-alibaba-ram[Create the required Alibaba Cloud resources].
|
||||
|
||||
@@ -8,11 +8,7 @@ toc::[]
|
||||
|
||||
You can install {product-title} on on-premise hardware or on-premise VMs by using the {ai-full}. Installing {product-title} by using the {ai-full} supports `x86_64`, `AArch64`, `ppc64le`, and `s390x` CPU architectures.
|
||||
|
||||
The {ai-full} is a user-friendly installation solution offered on the Red{nbsp}Hat Hybrid Cloud Console. The {ai-full} supports the various deployment platforms with a focus on the following infrastructures:
|
||||
|
||||
* Bare metal
|
||||
* Nutanix
|
||||
* vSphere
|
||||
The {ai-full} is a user-friendly installation solution offered on the Red{nbsp}Hat Hybrid Cloud Console.
|
||||
|
||||
[role="_additional-resources"]
|
||||
[id="additional-resources_installing-vsphere-assisted-installer"]
|
||||
|
||||
@@ -7,7 +7,6 @@
|
||||
//Platforms that must use `ccoctl` and update content
|
||||
// * installing/installing_ibm_cloud_public/configuring-iam-ibm-cloud.adoc
|
||||
// * installing/installing_ibm_powervs/preparing-to-install-on-ibm-power-vs.doc
|
||||
// * installing/installing_alibaba/manually-creating-alibaba-ram.adoc
|
||||
// * installing/installing_nutanix/preparing-to-install-on-nutanix.adoc
|
||||
//
|
||||
// AWS assemblies:
|
||||
@@ -49,9 +48,6 @@ endif::[]
|
||||
ifeval::["{context}" == "configuring-iam-ibm-cloud"]
|
||||
:ibm-cloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "manually-creating-alibaba-ram"]
|
||||
:alibabacloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "preparing-to-install-on-nutanix"]
|
||||
:nutanix:
|
||||
endif::[]
|
||||
@@ -133,11 +129,6 @@ endif::[]
|
||||
ifndef::update[= Configuring the Cloud Credential Operator utility]
|
||||
ifdef::update[= Configuring the Cloud Credential Operator utility for a cluster update]
|
||||
|
||||
//This applies only to Alibaba Cloud.
|
||||
ifdef::alibabacloud[]
|
||||
To assign RAM users and policies that provide long-term RAM AccessKeys (AKs) for each in-cluster component, extract and prepare the Cloud Credential Operator (CCO) utility (`ccoctl`) binary.
|
||||
endif::alibabacloud[]
|
||||
|
||||
//Nutanix-only intro because it needs context in its install procedure.
|
||||
ifdef::nutanix[]
|
||||
The Cloud Credential Operator (CCO) manages cloud provider credentials as Kubernetes custom resource definitions (CRDs). To install a cluster on Nutanix, you must set the CCO to `manual` mode as part of the installation process.
|
||||
@@ -396,7 +387,6 @@ Usage:
|
||||
ccoctl [command]
|
||||
|
||||
Available Commands:
|
||||
alibabacloud Manage credentials objects for alibaba cloud
|
||||
aws Manage credentials objects for AWS cloud
|
||||
azure Manage credentials objects for Azure
|
||||
gcp Manage credentials objects for Google cloud
|
||||
@@ -422,9 +412,6 @@ endif::[]
|
||||
ifeval::["{context}" == "configuring-iam-ibm-cloud"]
|
||||
:!ibm-cloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "manually-creating-alibaba-ram"]
|
||||
:!alibabacloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "preparing-to-install-on-nutanix"]
|
||||
:!nutanix:
|
||||
endif::[]
|
||||
|
||||
@@ -1,10 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// Platforms that must use `ccoctl`
|
||||
// * installing/installing_alibaba/manually-creating-alibaba-ram.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
//
|
||||
// AWS assemblies:
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
// * installing/installing_aws/installing-aws-network-customizations.adoc
|
||||
@@ -32,17 +27,6 @@
|
||||
// * installing/installing_azure/installing-azure-vnet.adoc
|
||||
// * installing/installing_azure/installing-restricted-networks-azure-installer-provisioned.adoc
|
||||
|
||||
//Platforms that must use `ccoctl`
|
||||
ifeval::["{context}" == "installing-alibaba-default"]
|
||||
:alibabacloud-default:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-customizations"]
|
||||
:alibabacloud-customizations:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-vpc"]
|
||||
:alibabacloud-vpc:
|
||||
endif::[]
|
||||
|
||||
//AWS install assemblies
|
||||
ifeval::["{context}" == "installing-aws-customizations"]
|
||||
:aws-sts:
|
||||
@@ -132,12 +116,6 @@ ifdef::azure-workload-id[]
|
||||
|
||||
You can use the `ccoctl azure create-all` command to automate the creation of Azure resources.
|
||||
endif::azure-workload-id[]
|
||||
ifdef::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
|
||||
[id="cco-ccoctl-creating-at-once_{context}"]
|
||||
= Creating credentials for {product-title} components with the ccoctl tool
|
||||
|
||||
You can use the {product-title} Cloud Credential Operator (CCO) utility to automate the creation of Alibaba Cloud RAM users and policies for each in-cluster component.
|
||||
endif::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
@@ -149,10 +127,7 @@ By default, `ccoctl` creates objects in the directory in which the commands are
|
||||
You must have:
|
||||
|
||||
* Extracted and prepared the `ccoctl` binary.
|
||||
ifdef::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
|
||||
* Created a RAM user with sufficient permission to create the {product-title} cluster.
|
||||
* Added the AccessKeyID (`access_key_id`) and AccessKeySecret (`access_key_secret`) of that RAM user into the link:https://www.alibabacloud.com/help/en/doc-detail/311667.htm#h2-sls-mfm-3p3[`~/.alibabacloud/credentials` file] on your local computer.
|
||||
endif::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
|
||||
|
||||
ifdef::azure-workload-id[]
|
||||
* Access to your Microsoft Azure account by using the Azure CLI.
|
||||
endif::azure-workload-id[]
|
||||
@@ -267,77 +242,6 @@ To see additional optional parameters and explanations of how to use them, run t
|
||||
====
|
||||
endif::azure-workload-id[]
|
||||
|
||||
ifdef::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
|
||||
. Use the `ccoctl` tool to process all `CredentialsRequest` objects by running the following command:
|
||||
|
||||
.. Run the following command to use the tool:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ ccoctl alibabacloud create-ram-users \
|
||||
--name <name> \// <1>
|
||||
--region=<alibaba_region> \// <2>
|
||||
--credentials-requests-dir=<path_to_credentials_requests_directory> \// <3>
|
||||
--output-dir=<path_to_ccoctl_output_dir> <4>
|
||||
----
|
||||
<1> Specify the name used to tag any cloud resources that are created for tracking.
|
||||
<2> Specify the Alibaba Cloud region in which cloud resources will be created.
|
||||
<3> Specify the directory containing the files for the component `CredentialsRequest` objects.
|
||||
<4> Specify the directory where the generated component credentials secrets will be placed.
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
|
||||
====
|
||||
+
|
||||
.Example output
|
||||
[source,text]
|
||||
----
|
||||
2022/02/11 16:18:26 Created RAM User: user1-alicloud-openshift-machine-api-alibabacloud-credentials
|
||||
2022/02/11 16:18:27 Ready for creating new ram policy user1-alicloud-openshift-machine-api-alibabacloud-credentials-policy-policy
|
||||
2022/02/11 16:18:27 RAM policy user1-alicloud-openshift-machine-api-alibabacloud-credentials-policy-policy has created
|
||||
2022/02/11 16:18:28 Policy user1-alicloud-openshift-machine-api-alibabacloud-credentials-policy-policy has attached on user user1-alicloud-openshift-machine-api-alibabacloud-credentials
|
||||
2022/02/11 16:18:29 Created access keys for RAM User: user1-alicloud-openshift-machine-api-alibabacloud-credentials
|
||||
2022/02/11 16:18:29 Saved credentials configuration to: user1-alicloud/manifests/openshift-machine-api-alibabacloud-credentials-credentials.yaml
|
||||
...
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
A RAM user can have up to two AccessKeys at the same time. If you run `ccoctl alibabacloud create-ram-users` more than twice, the previously generated manifests secret becomes stale and you must reapply the newly generated secrets.
|
||||
====
|
||||
|
||||
.. Verify that the {product-title} secrets are created:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ ls <path_to_ccoctl_output_dir>/manifests
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
[source,text]
|
||||
----
|
||||
openshift-cluster-csi-drivers-alibaba-disk-credentials-credentials.yaml
|
||||
openshift-image-registry-installer-cloud-credentials-credentials.yaml
|
||||
openshift-ingress-operator-cloud-credentials-credentials.yaml
|
||||
openshift-machine-api-alibabacloud-credentials-credentials.yaml
|
||||
----
|
||||
+
|
||||
You can verify that the RAM users and policies are created by querying Alibaba Cloud. For more information, refer to Alibaba Cloud documentation on listing RAM users and policies.
|
||||
|
||||
. Copy the generated credential files to the target manifests directory:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ cp ./<path_to_ccoctl_output_dir>/manifests/*credentials.yaml ./<path_to_installation>dir>/manifests/
|
||||
----
|
||||
+
|
||||
where:
|
||||
|
||||
`<path_to_ccoctl_output_dir>`:: Specifies the directory created by the `ccoctl alibabacloud create-ram-users` command.
|
||||
`<path_to_installation_dir>`:: Specifies the directory in which the installation program creates files.
|
||||
endif::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
|
||||
|
||||
ifdef::aws-sts,google-cloud-platform,azure-workload-id[]
|
||||
.Verification
|
||||
|
||||
@@ -403,17 +307,6 @@ openshift-machine-api-azure-cloud-credentials-credentials.yaml
|
||||
You can verify that the Microsoft Entra ID service accounts are created by querying Azure. For more information, refer to Azure documentation on listing Entra ID service accounts.
|
||||
endif::azure-workload-id[]
|
||||
|
||||
//Platforms that must use `ccoctl`
|
||||
ifeval::["{context}" == "installing-alibaba-default"]
|
||||
:!alibabacloud-default:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-customizations"]
|
||||
:!alibabacloud-customizations:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-vpc"]
|
||||
:!alibabacloud-vpc:
|
||||
endif::[]
|
||||
|
||||
//AWS install assemblies
|
||||
ifeval::["{context}" == "installing-aws-customizations"]
|
||||
:!aws-sts:
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * cli_reference/openshift_cli/getting-started.adoc
|
||||
// * installing/installing_aws/installing-aws-user-infra.adoc
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_aws/installing-aws-user-infra.adoc
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
// * installing/installing_aws/installing-aws-default.adoc
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc
|
||||
// * installing/installing_bare_metal/installing-bare-metal.adoc
|
||||
// * installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc
|
||||
// * installing/installing_bare_metal/installing-bare-metal.adoc
|
||||
// * installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc
|
||||
|
||||
@@ -1,67 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-customizations.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="installation-alibaba-config-yaml_{context}"]
|
||||
= Sample customized install-config.yaml file for Alibaba Cloud
|
||||
|
||||
You can customize the installation configuration file (`install-config.yaml`) to specify more details about
|
||||
your cluster's platform or modify the values of the required
|
||||
parameters.
|
||||
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: v1
|
||||
baseDomain: alicloud-dev.devcluster.openshift.com
|
||||
credentialsMode: Manual
|
||||
compute:
|
||||
- architecture: amd64
|
||||
hyperthreading: Enabled
|
||||
name: worker
|
||||
platform: {}
|
||||
replicas: 3
|
||||
controlPlane:
|
||||
architecture: amd64
|
||||
hyperthreading: Enabled
|
||||
name: master
|
||||
platform: {}
|
||||
replicas: 3
|
||||
metadata:
|
||||
creationTimestamp: null
|
||||
name: test-cluster <1>
|
||||
networking:
|
||||
clusterNetwork:
|
||||
- cidr: 10.128.0.0/14
|
||||
hostPrefix: 23
|
||||
machineNetwork:
|
||||
- cidr: 10.0.0.0/16
|
||||
networkType: OVNKubernetes <2>
|
||||
serviceNetwork:
|
||||
- 172.30.0.0/16
|
||||
platform:
|
||||
alibabacloud:
|
||||
defaultMachinePlatform: <3>
|
||||
instanceType: ecs.g6.xlarge
|
||||
systemDiskCategory: cloud_efficiency
|
||||
systemDiskSize: 200
|
||||
region: ap-southeast-1 <4>
|
||||
resourceGroupID: rg-acfnw6j3hyai <5>
|
||||
vpcID: vpc-0xifdjerdibmaqvtjob2b <8>
|
||||
vswitchIDs: <8>
|
||||
- vsw-0xi8ycgwc8wv5rhviwdq5
|
||||
- vsw-0xiy6v3z2tedv009b4pz2
|
||||
publish: External
|
||||
pullSecret: '{"auths": {"cloud.openshift.com": {"auth": ... }' <6>
|
||||
sshKey: |
|
||||
ssh-rsa AAAA... <7>
|
||||
----
|
||||
<1> Required. The installation program prompts you for a cluster name.
|
||||
<2> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
|
||||
<3> Optional. Specify parameters for machine pools that do not define their own platform configuration.
|
||||
<4> Required. The installation program prompts you for the region to deploy the cluster to.
|
||||
<5> Optional. Specify an existing resource group where the cluster should be installed.
|
||||
<6> Required. The installation program prompts you for the pull secret.
|
||||
<7> Optional. The installation program prompts you for the SSH key value that you use to access the machines in your cluster.
|
||||
<8> Optional. These are example vswitchID values.
|
||||
@@ -1,37 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-account.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="installation-alibaba-dns_{context}"]
|
||||
= Registering and Configuring Alibaba Cloud Domain
|
||||
|
||||
To install {product-title}, the Alibaba Cloud account you use must have a dedicated public hosted zone in your account. This zone must be authoritative for the domain. This service provides cluster DNS resolution and name lookup for external connections to the cluster.
|
||||
|
||||
.Procedure
|
||||
|
||||
. Identify your domain, or subdomain, and registrar. You can transfer an existing domain and registrar or obtain a new one through Alibaba Cloud or another source.
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
If you purchase a new domain through Alibaba Cloud, it takes time for the relevant DNS changes to propagate. For more information about purchasing domains through Alibaba Cloud, see link:https://www.alibabacloud.com/domain[Alibaba Cloud domains].
|
||||
====
|
||||
|
||||
. If you are using an existing domain and registrar, migrate its DNS to Alibaba Cloud. See link:https://www.alibabacloud.com/help/en/doc-detail/42479.htm[Domain name transfer]
|
||||
in the Alibaba Cloud documentation.
|
||||
|
||||
. Configure DNS for your domain. This includes:
|
||||
* link:https://partners-intl.aliyun.com/help/en/doc-detail/54068.htm?spm=a2c63.p38356.0.0.427d2054k5gZOr#task-1830383[Registering a generic domain name].
|
||||
* link:https://partners-intl.aliyun.com/help/en/doc-detail/108953.htm?spm=a2c63.p38356.0.0.3c62433fjUrdZG#section-qyn-s41-ygb[Completing real-name verification for your domain name].
|
||||
* link:https://account.alibabacloud.com/login/login.htm[Applying for an Internet Content Provider (ICP) filing].
|
||||
* link:https://www.alibabacloud.com/product/dns/pricing?spm=a3c0i.23458820.2359477120.2.36ca7d3fe0b5KL[Enabling domain name resolution].
|
||||
+
|
||||
Use an appropriate root domain, such as `openshiftcorp.com`, or subdomain, such as `clusters.openshiftcorp.com`.
|
||||
|
||||
. If you are using a subdomain, follow the procedures of your company to add its delegation records to the parent domain.
|
||||
|
||||
////
|
||||
.Question
|
||||
|
||||
Can Alibaba provide a link(s) to their doc on how to complete each task under step 3 in their doc? Could not find content in their help.
|
||||
////
|
||||
@@ -1,15 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-account.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="installation-alibaba-regions_{context}"]
|
||||
= Supported Alibaba regions
|
||||
|
||||
You can deploy an {product-title} cluster to the regions listed in the link:https://www.alibabacloud.com/help/en/doc-detail/188196.htm[Alibaba _Regions and zones_ documentation].
|
||||
|
||||
////
|
||||
Answer from Gaurav Singh (PM)
|
||||
|
||||
All of the regions (in mainland china and outside mainland china ) listed in this doc https://www.alibabacloud.com/help/doc-detail/188196.htm[Alibaba doc] will be shown as option to the customer to deploy openshift . We might need to test all of them.
|
||||
////
|
||||
@@ -7,7 +7,6 @@
|
||||
// * installing/installing_azure_stack_hub/installation-config-parameters-ash.adoc
|
||||
// * installing/installing_bare_metal/installation-config-parameters-bare-metal.adoc
|
||||
// * installing/installing_ibm_cloud_public/installation-config-parameters-ibm-cloud-vps.adoc
|
||||
// * installing/installing_alibaba/installation-config-parameters-alibaba.adoc
|
||||
// * installing/installing_ibm_powervs/installation-config-parameters-ibm-power-vs.adoc
|
||||
// * installing/installing_nutanix/installation-config-parameters-nutanix.adoc
|
||||
// * installing/installing_openstack/installation-config-parameters-openstack.adoc
|
||||
@@ -36,9 +35,6 @@ endif::[]
|
||||
ifeval::["{context}" == "installation-config-parameters-ibm-cloud-vpc"]
|
||||
:ibm-cloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installation-config-parameters-alibaba"]
|
||||
:alibaba-cloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installation-config-parameters-ibm-power-vs"]
|
||||
:ibm-power-vs:
|
||||
endif::[]
|
||||
@@ -125,7 +121,7 @@ endif::osp[]
|
||||
|
||||
|platform:
|
||||
ifndef::agent[]
|
||||
|The configuration for the specific platform upon which to perform the installation: `alibabacloud`, `aws`, `baremetal`, `azure`, `gcp`, `ibmcloud`, `nutanix`, `openstack`, `powervs`, `vsphere`, or `{}`. For additional information about `platform.<platform>` parameters, consult the table for your specific platform that follows.
|
||||
|The configuration for the specific platform upon which to perform the installation: `aws`, `baremetal`, `azure`, `gcp`, `ibmcloud`, `nutanix`, `openstack`, `powervs`, `vsphere`, or `{}`. For additional information about `platform.<platform>` parameters, consult the table for your specific platform that follows.
|
||||
endif::agent[]
|
||||
ifdef::agent[]
|
||||
|The configuration for the specific platform upon which to perform the installation: `baremetal`, `external`, `none`, or `vsphere`.
|
||||
@@ -528,7 +524,7 @@ ifdef::ibm-power-vs[]
|
||||
Example usage, `compute.platform.powervs.sysType`.
|
||||
endif::ibm-power-vs[]
|
||||
ifndef::agent[]
|
||||
|`alibabacloud`, `aws`, `azure`, `gcp`, `ibmcloud`, `nutanix`, `openstack`, `powervs`, `vsphere`, or `{}`
|
||||
|`aws`, `azure`, `gcp`, `ibmcloud`, `nutanix`, `openstack`, `powervs`, `vsphere`, or `{}`
|
||||
endif::agent[]
|
||||
ifdef::agent[]
|
||||
|`baremetal`, `vsphere`, or `{}`
|
||||
@@ -622,7 +618,7 @@ ifdef::ibm-power-vs[]
|
||||
Example usage, `controlPlane.platform.powervs.processors`.
|
||||
endif::ibm-power-vs[]
|
||||
ifndef::agent[]
|
||||
|`alibabacloud`, `aws`, `azure`, `gcp`, `ibmcloud`, `nutanix`, `openstack`, `powervs`, `vsphere`, or `{}`
|
||||
|`aws`, `azure`, `gcp`, `ibmcloud`, `nutanix`, `openstack`, `powervs`, `vsphere`, or `{}`
|
||||
endif::agent[]
|
||||
ifdef::agent[]
|
||||
|`baremetal`, `vsphere`, or `{}`
|
||||
@@ -3106,171 +3102,6 @@ configuring user-defined routing.
|
||||
|====
|
||||
endif::ash[]
|
||||
|
||||
ifdef::alibaba-cloud[]
|
||||
//From: https://github.com/openshift/installer/blob/master/data/data/install.openshift.io_installconfigs.yaml#L20; https://github.com/openshift/openshift-docs/pull/40651/files#r792388476
|
||||
|
||||
[id="installation-configuration-parameters-additional-alibaba_{context}"]
|
||||
== Additional Alibaba Cloud configuration parameters
|
||||
|
||||
Additional Alibaba Cloud configuration parameters are described in the following table. The `alibabacloud` parameters are the configuration used when installing on Alibaba Cloud. The `defaultMachinePlatform` parameters are the default configuration used when installing on Alibaba Cloud for machine pools that do not define their own platform configuration.
|
||||
|
||||
These parameters apply to both compute machines and control plane machines where specified.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
If defined, the parameters `compute.platform.alibabacloud` and `controlPlane.platform.alibabacloud` will overwrite `platform.alibabacloud.defaultMachinePlatform` settings for compute machines and control plane machines respectively.
|
||||
====
|
||||
|
||||
.Optional {alibaba} parameters
|
||||
[cols=".^2l,.^3,.^5a",options="header"]
|
||||
|====
|
||||
|Parameter|Description|Values
|
||||
|
||||
|compute:
|
||||
platform:
|
||||
alibabacloud:
|
||||
imageID:
|
||||
|The imageID used to create the ECS instance. ImageID must belong to the same region as the cluster.
|
||||
|String.
|
||||
|
||||
|compute:
|
||||
platform:
|
||||
alibabacloud:
|
||||
instanceType:
|
||||
|InstanceType defines the ECS instance type. Example: `ecs.g6.large`
|
||||
|String.
|
||||
|
||||
|compute:
|
||||
platform:
|
||||
alibabacloud:
|
||||
systemDiskCategory:
|
||||
|Defines the category of the system disk. Examples: `cloud_efficiency`,`cloud_essd`
|
||||
|String.
|
||||
|
||||
|compute:
|
||||
platform:
|
||||
alibabacloud:
|
||||
systemDisksize:
|
||||
|Defines the size of the system disk in gibibytes (GiB).
|
||||
|Integer.
|
||||
|
||||
|compute:
|
||||
platform:
|
||||
alibabacloud:
|
||||
zones:
|
||||
|The list of availability zones that can be used. Examples: `cn-hangzhou-h`, `cn-hangzhou-j`
|
||||
|String list.
|
||||
|
||||
|controlPlane:
|
||||
platform:
|
||||
alibabacloud:
|
||||
imageID:
|
||||
|The imageID used to create the ECS instance. ImageID must belong to the same region as the cluster.
|
||||
|String.
|
||||
|
||||
|controlPlane:
|
||||
platform:
|
||||
alibabacloud:
|
||||
instanceType:
|
||||
|InstanceType defines the ECS instance type. Example: `ecs.g6.xlarge`
|
||||
|String.
|
||||
|
||||
|controlPlane:
|
||||
platform:
|
||||
alibabacloud:
|
||||
systemDiskCategory:
|
||||
|Defines the category of the system disk. Examples: `cloud_efficiency`,`cloud_essd`
|
||||
|String.
|
||||
|
||||
|controlPlane:
|
||||
platform:
|
||||
alibabacloud:
|
||||
systemDisksize:
|
||||
|Defines the size of the system disk in gibibytes (GiB).
|
||||
|Integer.
|
||||
|
||||
|controlPlane:
|
||||
platform:
|
||||
alibabacloud:
|
||||
zones:
|
||||
|The list of availability zones that can be used. Examples: `cn-hangzhou-h`, `cn-hangzhou-j`
|
||||
|String list.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
region:
|
||||
|Required. The Alibaba Cloud region where the cluster will be created.
|
||||
|String.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
resourceGroupID:
|
||||
|The ID of an already existing resource group where the cluster will be installed. If empty, the installation program will create a new resource group for the cluster.
|
||||
|String.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
tags:
|
||||
|Additional keys and values to apply to all Alibaba Cloud resources created for the cluster.
|
||||
|Object.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
vpcID:
|
||||
|The ID of an already existing VPC where the cluster should be installed. If empty, the installation program will create a new VPC for the cluster.
|
||||
|String.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
vswitchIDs:
|
||||
|The ID list of already existing VSwitches where cluster resources will be created. The existing VSwitches can only be used when also using existing VPC. If empty, the installation program will create new VSwitches for the cluster.
|
||||
|String list.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
defaultMachinePlatform:
|
||||
imageID:
|
||||
|For both compute machines and control plane machines, the image ID that should be used to create ECS instance. If set, the image ID should belong to the same region as the cluster.
|
||||
|String.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
defaultMachinePlatform:
|
||||
instanceType:
|
||||
|For both compute machines and control plane machines, the ECS instance type used to create the ECS instance. Example: `ecs.g6.xlarge`
|
||||
|String.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
defaultMachinePlatform:
|
||||
systemDiskCategory:
|
||||
|For both compute machines and control plane machines, the category of the system disk. Examples: `cloud_efficiency`, `cloud_essd`.
|
||||
|String, for example "", `cloud_efficiency`, `cloud_essd`.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
defaultMachinePlatform:
|
||||
systemDiskSize:
|
||||
|For both compute machines and control plane machines, the size of the system disk in gibibytes (GiB). The minimum is `120`.
|
||||
|Integer.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
defaultMachinePlatform:
|
||||
zones:
|
||||
|For both compute machines and control plane machines, the list of availability zones that can be used. Examples: `cn-hangzhou-h`, `cn-hangzhou-j`
|
||||
|String list.
|
||||
|
||||
|platform:
|
||||
alibabacloud:
|
||||
privateZoneID:
|
||||
|The ID of an existing private zone into which to add DNS records for the cluster's internal API. An existing private zone can only be used when also using existing VPC. The private zone must be associated with the VPC containing the subnets. Leave the private zone unset to have the installation program create the private zone on your behalf.
|
||||
|String.
|
||||
|
||||
|====
|
||||
|
||||
endif::alibaba-cloud[]
|
||||
|
||||
ifdef::nutanix[]
|
||||
[id="installation-configuration-parameters-additional-nutanix_{context}"]
|
||||
== Additional Nutanix configuration parameters
|
||||
@@ -3547,9 +3378,6 @@ endif::[]
|
||||
ifeval::["{context}" == "installation-config-parameters-ibm-cloud-vpc"]
|
||||
:!ibm-cloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installation-config-parameters-alibaba"]
|
||||
:!alibaba-cloud:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installation-config-parameters-ibm-power-vs"]
|
||||
:!ibm-power-vs:
|
||||
endif::[]
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_aws/installing_aws-customizations.adoc
|
||||
// * installing/installing_aws/installing_aws-network-customizations.adoc
|
||||
// * installing/installing_aws/installing_aws-private.adoc
|
||||
|
||||
@@ -1,52 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
|
||||
:_mod-docs-content-type: CONCEPT
|
||||
[id="installation-custom-alibaba-vpc_{context}"]
|
||||
= Using a custom VPC
|
||||
|
||||
In {product-title} {product-version}, you can deploy a cluster into existing subnets in an existing Virtual Private Cloud (VPC) in the Alibaba Cloud Platform. By deploying {product-title} into an existing Alibaba VPC, you can avoid limit constraints in new accounts and more easily adhere to your organization's operational constraints. If you cannot obtain the infrastructure creation permissions that are required to create the VPC yourself, use this installation option. You must configure networking using vSwitches.
|
||||
|
||||
[id="installation-custom-alibaba-vpc-requirements_{context}"]
|
||||
== Requirements for using your VPC
|
||||
|
||||
The union of the VPC CIDR block and the machine network CIDR must be non-empty. The vSwitches must be within the machine network.
|
||||
|
||||
The installation program does not create the following components:
|
||||
|
||||
* VPC
|
||||
* vSwitches
|
||||
* Route table
|
||||
* NAT gateway
|
||||
|
||||
include::snippets/custom-dns-server.adoc[]
|
||||
|
||||
[id="installation-custom-alibaba-vpc-validation_{context}"]
|
||||
== VPC validation
|
||||
|
||||
To ensure that the vSwitches you provide are suitable, the installation program confirms the following data:
|
||||
|
||||
* All the vSwitches that you specify must exist.
|
||||
* You have provided one or more vSwitches for control plane machines and compute machines.
|
||||
* The vSwitches' CIDRs belong to the machine CIDR that you specified.
|
||||
|
||||
[id="installation-about-custom-alibaba-permissions_{context}"]
|
||||
== Division of permissions
|
||||
|
||||
Some individuals can create different resources in your cloud than others. For example, you might be able to create application-specific items, like instances, buckets, and load balancers, but not networking-related components, such as VPCs or vSwitches.
|
||||
|
||||
[id="installation-custom-alibaba-vpc-isolation_{context}"]
|
||||
== Isolation between clusters
|
||||
|
||||
If you deploy {product-title} into an existing network, the isolation of cluster services is reduced in the following ways:
|
||||
|
||||
* You can install multiple {product-title} clusters in the same VPC.
|
||||
|
||||
* ICMP ingress is allowed to the entire network.
|
||||
|
||||
* TCP 22 ingress (SSH) is allowed to the entire network.
|
||||
|
||||
* Control plane TCP 6443 ingress (Kubernetes API) is allowed to the entire network.
|
||||
|
||||
* Control plane TCP 22623 ingress (MCS) is allowed to the entire network.
|
||||
@@ -1,9 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_aws/installing-alibaba-default.adoc
|
||||
// * installing/installing_aws/installing-alibaba-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_aws/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
// * installing/installing_aws/installing-aws-network-customizations.adoc
|
||||
// * installing/installing_aws/installing-aws-vpc.adoc
|
||||
@@ -44,15 +40,6 @@
|
||||
// Consider also adding the installation-configuration-parameters.adoc module.
|
||||
//YOU MUST SET AN IFEVAL FOR EACH NEW MODULE
|
||||
|
||||
ifeval::["{context}" == "installing-alibaba-default"]
|
||||
:alibabacloud-default:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-customizations"]
|
||||
:alibabacloud-custom:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-vpc"]
|
||||
:alibabacloud-vpc:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-aws-customizations"]
|
||||
:aws:
|
||||
:three-node-cluster:
|
||||
@@ -183,9 +170,6 @@ endif::[]
|
||||
= Creating the installation configuration file
|
||||
|
||||
You can customize the {product-title} cluster you install on
|
||||
ifdef::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
Alibaba Cloud.
|
||||
endif::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
ifdef::aws[]
|
||||
Amazon Web Services (AWS).
|
||||
endif::aws[]
|
||||
@@ -279,12 +263,6 @@ endif::ibm-power-vs[]
|
||||
====
|
||||
For production {product-title} clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your `ssh-agent` process uses.
|
||||
====
|
||||
ifdef::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
... Select *alibabacloud* as the platform to target.
|
||||
... Select the region to deploy the cluster to.
|
||||
... Select the base domain to deploy the cluster to. The base domain corresponds to the public DNS zone that you created for your cluster.
|
||||
... Provide a descriptive name for your cluster.
|
||||
endif::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
ifdef::aws[]
|
||||
... Select *AWS* as the platform to target.
|
||||
... If you do not have an Amazon Web Services (AWS) profile stored on your computer, enter the AWS
|
||||
@@ -386,7 +364,6 @@ The installation program connects to Prism Central.
|
||||
... Enter the base domain. This base domain must be the same one that you configured in the DNS records.
|
||||
endif::nutanix[]
|
||||
ifndef::osp[]
|
||||
ifndef::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
... Enter a descriptive name for your cluster.
|
||||
ifdef::azure[]
|
||||
+
|
||||
@@ -404,7 +381,6 @@ ifdef::vsphere,nutanix[]
|
||||
The cluster name you enter must match the cluster name you specified when configuring the DNS records.
|
||||
|
||||
endif::vsphere,nutanix[]
|
||||
endif::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
endif::osp[]
|
||||
ifdef::osp[]
|
||||
... Enter a name for your cluster. The name must be 14 or fewer characters long.
|
||||
@@ -419,9 +395,9 @@ ifdef::aws-outposts[]
|
||||
You will find more information about how to change these values below.
|
||||
endif::aws-outposts[]
|
||||
|
||||
ifndef::restricted,alibabacloud-default,alibabacloud-custom,alibabacloud-vpc,nutanix,aws-outposts[]
|
||||
ifndef::restricted,nutanix,aws-outposts[]
|
||||
. Modify the `install-config.yaml` file. You can find more information about the available parameters in the "Installation configuration parameters" section.
|
||||
endif::restricted,alibabacloud-default,alibabacloud-custom,alibabacloud-vpc,nutanix,aws-outposts[]
|
||||
endif::restricted,nutanix,aws-outposts[]
|
||||
ifdef::three-node-cluster[]
|
||||
+
|
||||
[NOTE]
|
||||
@@ -430,28 +406,6 @@ If you are installing a three-node cluster, be sure to set the `compute.replicas
|
||||
====
|
||||
endif::three-node-cluster[]
|
||||
|
||||
ifdef::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
. Installing the cluster into Alibaba Cloud requires that the Cloud Credential Operator (CCO) operate in manual mode. Modify the `install-config.yaml` file to set the `credentialsMode` parameter to `Manual`:
|
||||
+
|
||||
.Example install-config.yaml configuration file with `credentialsMode` set to `Manual`
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: v1
|
||||
baseDomain: cluster1.example.com
|
||||
credentialsMode: Manual <1>
|
||||
compute:
|
||||
- architecture: amd64
|
||||
hyperthreading: Enabled
|
||||
...
|
||||
----
|
||||
<1> Add this line to set the `credentialsMode` to `Manual`.
|
||||
endif::alibabacloud-default,alibabacloud-custom,alibabacloud-vpc[]
|
||||
|
||||
ifdef::alibabacloud-custom,alibabacloud-vpc[]
|
||||
. Modify the `install-config.yaml` file. You can find more information about the available parameters in the "Installation configuration parameters" section.
|
||||
endif::alibabacloud-custom,alibabacloud-vpc[]
|
||||
|
||||
|
||||
ifdef::osp+restricted[]
|
||||
. In the `install-config.yaml` file, set the value of `platform.openstack.clusterOSImage` to the image location or name. For example:
|
||||
+
|
||||
@@ -679,15 +633,6 @@ endif::azure[]
|
||||
|
||||
ifdef::osp-user[You now have the file `install-config.yaml` in the directory that you specified.]
|
||||
|
||||
ifeval::["{context}" == "installing-alibaba-default"]
|
||||
:!alibabacloud-default:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-customizations"]
|
||||
:!alibabacloud-custom:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-vpc"]
|
||||
:!alibabacloud-vpc:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-aws-customizations"]
|
||||
:!aws:
|
||||
:!three-node-cluster:
|
||||
|
||||
@@ -1,9 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-default.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
// * installing/installing_aws/installing-aws-default.adoc
|
||||
// * installing/installing_aws/installing-aws-government-region.adoc
|
||||
@@ -50,22 +46,6 @@
|
||||
// If you use this module in any other assembly, you must update the ifeval
|
||||
// statements.
|
||||
|
||||
ifeval::["{context}" == "installing-alibaba-customizations"]
|
||||
:custom-config:
|
||||
:single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-default"]
|
||||
:custom-config:
|
||||
:single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-network-customizations"]
|
||||
:custom-config:
|
||||
:single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-vpc"]
|
||||
:custom-config:
|
||||
:single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-aws-private"]
|
||||
:custom-config:
|
||||
:aws:
|
||||
@@ -555,22 +535,6 @@ INFO Time elapsed: 36m22s
|
||||
* It is recommended that you use Ignition config files within 12 hours after they are generated because the 24-hour certificate rotates from 16 to 22 hours after the cluster is installed. By using the Ignition config files within 12 hours, you can avoid installation failure if the certificate update runs during installation.
|
||||
====
|
||||
|
||||
ifeval::["{context}" == "installing-alibaba-customizations"]
|
||||
:!custom-config:
|
||||
:!single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-default"]
|
||||
:!custom-config:
|
||||
:!single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-network-customizations"]
|
||||
:!custom-config:
|
||||
:!single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-alibaba-vpc"]
|
||||
:!custom-config:
|
||||
:!single-step:
|
||||
endif::[]
|
||||
ifeval::["{context}" == "installing-aws-private"]
|
||||
:!custom-config:
|
||||
:!aws:
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_aws/installing-aws-user-infra.adoc
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
// * installing/installing_aws/installing-aws-default.adoc
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_aws/installing-aws-china.adoc.
|
||||
// * installing/installing_aws/installing-aws-secret-region.adoc
|
||||
// *installing/validating-an-installation.adoc
|
||||
|
||||
@@ -1,24 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-default.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="manually-creating-alibaba-manifests_{context}"]
|
||||
= Generating the required installation manifests
|
||||
|
||||
You must generate the Kubernetes manifest and Ignition config files that the cluster needs to configure the machines.
|
||||
|
||||
.Procedure
|
||||
|
||||
. Generate the manifests by running the following command from the directory that contains the installation program:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ openshift-install create manifests --dir <installation_directory>
|
||||
----
|
||||
+
|
||||
where:
|
||||
|
||||
`<installation_directory>`:: Specifies the directory in which the installation program creates files.
|
||||
@@ -1,247 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/manually-creating-alibaba-ram.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="manually-creating-alibaba-ram-user_{context}"]
|
||||
= Creating the required RAM user
|
||||
|
||||
// https://github.com/openshift/cloud-credential-operator/pull/412/files#diff-2480a11ca4927139d6eaa9883946b6f4cb38358cd98def8c57dd73e9319dbc9cR232
|
||||
|
||||
You must have a Alibaba Cloud Resource Access Management (RAM) user for the installation that has sufficient privileges. You can use the Alibaba Cloud Resource Access Management console to create a new user or modify an existing user. Later, you create credentials in {product-title} based on this user's permissions.
|
||||
|
||||
When you configure the RAM user, be sure to consider the following requirements:
|
||||
|
||||
* The user must have an Alibaba Cloud AccessKey ID and AccessKey secret pair.
|
||||
|
||||
** For a new user, you can select `Open API Access` for the Access Mode when creating the user. This mode generates the required AccessKey pair.
|
||||
** For an existing user, you can add an AccessKey pair or you can link:https://www.alibabacloud.com/help/en/doc-detail/53045.htm[obtain the AccessKey pair] for that user.
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
When created, the AccessKey secret is displayed only once. You must immediately save the AccessKey pair because the AccessKey pair is required for API calls.
|
||||
====
|
||||
|
||||
* Add the AccessKey ID and secret to the link:https://www.alibabacloud.com/help/en/doc-detail/311667.htm#h2-sls-mfm-3p3[`~/.alibabacloud/credentials` file] on your local computer. Alibaba Cloud automatically creates this file when you log in to the console. The Cloud Credential Operator (CCO) utility, ccoutil, uses these credentials when processing `Credential Request` objects.
|
||||
+
|
||||
For example:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
[default] # Default client
|
||||
type = access_key # Certification type: access_key
|
||||
access_key_id = LTAI5t8cefXKmt # Key <1>
|
||||
access_key_secret = wYx56mszAN4Uunfh # Secret
|
||||
----
|
||||
<1> Add your AccessKeyID and AccessKeySecret here.
|
||||
|
||||
* The RAM user must have the `AdministratorAccess` policy to ensure that the account has sufficient permission to create the {product-title} cluster. This policy grants permissions to manage all Alibaba Cloud resources.
|
||||
+
|
||||
When you attach the `AdministratorAccess` policy to a RAM user, you grant that user full access to all Alibaba Cloud services and resources. If you do not want to create a user with full access, create a custom policy with the following actions that you can add to your RAM user for installation. These actions are sufficient to install {product-title}.
|
||||
+
|
||||
[TIP]
|
||||
====
|
||||
You can copy and paste the following JSON code into the Alibaba Cloud console to create a custom poicy. For information on creating custom policies, see link:https://www.alibabacloud.com/help/en/doc-detail/93733.html[Create a custom policy] in the Alibaba Cloud documentation.
|
||||
====
|
||||
+
|
||||
.Example custom policy JSON file
|
||||
[%collapsible]
|
||||
====
|
||||
[source,json]
|
||||
----
|
||||
{
|
||||
"Version": "1",
|
||||
"Statement": [
|
||||
{
|
||||
"Action": [
|
||||
"tag:ListTagResources",
|
||||
"tag:UntagResources"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"vpc:DescribeVpcs",
|
||||
"vpc:DeleteVpc",
|
||||
"vpc:DescribeVSwitches",
|
||||
"vpc:DeleteVSwitch",
|
||||
"vpc:DescribeEipAddresses",
|
||||
"vpc:DescribeNatGateways",
|
||||
"vpc:ReleaseEipAddress",
|
||||
"vpc:DeleteNatGateway",
|
||||
"vpc:DescribeSnatTableEntries",
|
||||
"vpc:CreateSnatEntry",
|
||||
"vpc:AssociateEipAddress",
|
||||
"vpc:ListTagResources",
|
||||
"vpc:TagResources",
|
||||
"vpc:DescribeVSwitchAttributes",
|
||||
"vpc:CreateVSwitch",
|
||||
"vpc:CreateNatGateway",
|
||||
"vpc:DescribeRouteTableList",
|
||||
"vpc:CreateVpc",
|
||||
"vpc:AllocateEipAddress",
|
||||
"vpc:ListEnhanhcedNatGatewayAvailableZones"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"ecs:ModifyInstanceAttribute",
|
||||
"ecs:DescribeSecurityGroups",
|
||||
"ecs:DeleteSecurityGroup",
|
||||
"ecs:DescribeSecurityGroupReferences",
|
||||
"ecs:DescribeSecurityGroupAttribute",
|
||||
"ecs:RevokeSecurityGroup",
|
||||
"ecs:DescribeInstances",
|
||||
"ecs:DeleteInstances",
|
||||
"ecs:DescribeNetworkInterfaces",
|
||||
"ecs:DescribeInstanceRamRole",
|
||||
"ecs:DescribeUserData",
|
||||
"ecs:DescribeDisks",
|
||||
"ecs:ListTagResources",
|
||||
"ecs:AuthorizeSecurityGroup",
|
||||
"ecs:RunInstances",
|
||||
"ecs:TagResources",
|
||||
"ecs:ModifySecurityGroupPolicy",
|
||||
"ecs:CreateSecurityGroup",
|
||||
"ecs:DescribeAvailableResource",
|
||||
"ecs:DescribeRegions",
|
||||
"ecs:AttachInstanceRamRole"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"pvtz:DescribeRegions",
|
||||
"pvtz:DescribeZones",
|
||||
"pvtz:DeleteZone",
|
||||
"pvtz:DeleteZoneRecord",
|
||||
"pvtz:BindZoneVpc",
|
||||
"pvtz:DescribeZoneRecords",
|
||||
"pvtz:AddZoneRecord",
|
||||
"pvtz:SetZoneRecordStatus",
|
||||
"pvtz:DescribeZoneInfo",
|
||||
"pvtz:DescribeSyncEcsHostTask",
|
||||
"pvtz:AddZone"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"slb:DescribeLoadBalancers",
|
||||
"slb:SetLoadBalancerDeleteProtection",
|
||||
"slb:DeleteLoadBalancer",
|
||||
"slb:SetLoadBalancerModificationProtection",
|
||||
"slb:DescribeLoadBalancerAttribute",
|
||||
"slb:AddBackendServers",
|
||||
"slb:DescribeLoadBalancerTCPListenerAttribute",
|
||||
"slb:SetLoadBalancerTCPListenerAttribute",
|
||||
"slb:StartLoadBalancerListener",
|
||||
"slb:CreateLoadBalancerTCPListener",
|
||||
"slb:ListTagResources",
|
||||
"slb:TagResources",
|
||||
"slb:CreateLoadBalancer"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"ram:ListResourceGroups",
|
||||
"ram:DeleteResourceGroup",
|
||||
"ram:ListPolicyAttachments",
|
||||
"ram:DetachPolicy",
|
||||
"ram:GetResourceGroup",
|
||||
"ram:CreateResourceGroup",
|
||||
"ram:DeleteRole",
|
||||
"ram:GetPolicy",
|
||||
"ram:DeletePolicy",
|
||||
"ram:ListPoliciesForRole",
|
||||
"ram:CreateRole",
|
||||
"ram:AttachPolicyToRole",
|
||||
"ram:GetRole",
|
||||
"ram:CreatePolicy",
|
||||
"ram:CreateUser",
|
||||
"ram:DetachPolicyFromRole",
|
||||
"ram:CreatePolicyVersion",
|
||||
"ram:DetachPolicyFromUser",
|
||||
"ram:ListPoliciesForUser",
|
||||
"ram:AttachPolicyToUser",
|
||||
"ram:CreateUser",
|
||||
"ram:GetUser",
|
||||
"ram:DeleteUser",
|
||||
"ram:CreateAccessKey",
|
||||
"ram:ListAccessKeys",
|
||||
"ram:DeleteAccessKey",
|
||||
"ram:ListUsers",
|
||||
"ram:ListPolicyVersions"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"oss:DeleteBucket",
|
||||
"oss:DeleteBucketTagging",
|
||||
"oss:GetBucketTagging",
|
||||
"oss:GetBucketCors",
|
||||
"oss:GetBucketPolicy",
|
||||
"oss:GetBucketLifecycle",
|
||||
"oss:GetBucketReferer",
|
||||
"oss:GetBucketTransferAcceleration",
|
||||
"oss:GetBucketLog",
|
||||
"oss:GetBucketWebSite",
|
||||
"oss:GetBucketInfo",
|
||||
"oss:PutBucketTagging",
|
||||
"oss:PutBucket",
|
||||
"oss:OpenOssService",
|
||||
"oss:ListBuckets",
|
||||
"oss:GetService",
|
||||
"oss:PutBucketACL",
|
||||
"oss:GetBucketLogging",
|
||||
"oss:ListObjects",
|
||||
"oss:GetObject",
|
||||
"oss:PutObject",
|
||||
"oss:DeleteObject"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": [
|
||||
"alidns:DescribeDomainRecords",
|
||||
"alidns:DeleteDomainRecord",
|
||||
"alidns:DescribeDomains",
|
||||
"alidns:DescribeDomainRecordInfo",
|
||||
"alidns:AddDomainRecord",
|
||||
"alidns:SetDomainRecordStatus"
|
||||
],
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": "bssapi:CreateInstance",
|
||||
"Resource": "*",
|
||||
"Effect": "Allow"
|
||||
},
|
||||
{
|
||||
"Action": "ram:PassRole",
|
||||
"Resource": "*",
|
||||
"Effect": "Allow",
|
||||
"Condition": {
|
||||
"StringEquals": {
|
||||
"acs:Service": "ecs.aliyuncs.com"
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
----
|
||||
====
|
||||
|
||||
For more information about creating a RAM user and granting permissions, see link:https://www.alibabacloud.com/help/en/doc-detail/93720.htm[Create a RAM user] and link:https://www.alibabacloud.com/help/en/doc-detail/116146.htm[Grant permissions to a RAM user] in the Alibaba Cloud documentation.
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * installing/installing_alibaba/installing-alibaba-network-customizations.adoc
|
||||
// * installing/installing_alibaba/installing-alibaba-vpc.adoc
|
||||
// * installing/installing_aws/installing-aws-user-infra.adoc
|
||||
// * installing/installing_aws/installing-aws-china.adoc
|
||||
// * installing/installing_aws/installing-aws-customizations.adoc
|
||||
|
||||
@@ -3,7 +3,6 @@
|
||||
// * modules/installation-custom-aws-vpc.adoc
|
||||
// * modules/installation-about-custom-azure-vnet.adoc
|
||||
// * modules/installation-custom-gcp-vpc.adoc
|
||||
// * modules/installation-custom-alibaba-vpc.adoc
|
||||
// * modules/installation-ibm-power-vs.adoc
|
||||
|
||||
:_mod-docs-content-type: SNIPPET
|
||||
|
||||
@@ -72,15 +72,13 @@ Explore the following {product-title} installation tasks:
|
||||
|
||||
- **xref:../installing/index.adoc#ocp-installation-overview[{product-title} installation overview]**: Depending on the platform, you can install {product-title} on installer-provisioned or user-provisioned infrastructure. The {product-title} installation program provides the flexibility to deploy {product-title} on a range of different platforms.
|
||||
|
||||
- **xref:../installing/installing_alibaba/preparing-to-install-on-alibaba.adoc#preparing-to-install-on-alibaba[Install a cluster on Alibaba]**: On Alibaba Cloud, you can install {product-title} on installer-provisioned infrastructure. This is currently a Technology Preview feature only.
|
||||
|
||||
- **xref:../installing/installing_aws/preparing-to-install-on-aws.adoc#preparing-to-install-on-aws[Install a cluster on AWS]**: On AWS, you can install {product-title} on installer-provisioned infrastructure or user-provisioned infrastructure.
|
||||
|
||||
- **xref:../installing/installing_azure/preparing-to-install-on-azure.adoc#preparing-to-install-on-azure[Install a cluster on Azure]**: On Microsoft Azure, you can install {product-title} on installer-provisioned infrastructure or user-provisioned infrastructure.
|
||||
|
||||
- **xref:../installing/installing_azure_stack_hub/preparing-to-install-on-azure-stack-hub.adoc#preparing-to-install-on-azure-stack-hub[Install a cluster on Azure Stack Hub]**: On Microsoft Azure Stack Hub, you can install {product-title} on installer-provisioned infrastructure or user-provisioned infrastructure.
|
||||
|
||||
- **xref:../installing/installing_on_prem_assisted/installing-on-prem-assisted.html#using-the-assisted-installer_installing-on-prem-assisted[Installing {product-title} with the Assisted Installer]**: The Assisted Installer is an installation solution that is provided on the Red Hat {hybrid-console}. The Assisted Installer supports installing an {product-title} cluster on many platforms, but with a focus on bare metal, Nutanix, and {vmw-full} infrastructures.
|
||||
- **xref:../installing/installing_on_prem_assisted/installing-on-prem-assisted.html#using-the-assisted-installer_installing-on-prem-assisted[Installing {product-title} with the Assisted Installer]**: The Assisted Installer is an installation solution that is provided on the Red Hat {hybrid-console}. The Assisted Installer supports installing an {product-title} cluster on multiple platforms.
|
||||
|
||||
- **xref:../installing/installing_with_agent_based_installer/installing-with-agent-based-installer.html#installing-ocp-agent_installing-with-agent-based-installer[Installing {product-title} with the Agent-based Installer]**: You can use the Agent-based Installer to generate a bootable ISO image that contains the Assisted discovery agent, the Assisted Service, and all the other information required to deploy an {product-title} cluster. The Agent-based Installer leverages the advantages of the Assisted Installer in a disconnected environment
|
||||
|
||||
|
||||
Reference in New Issue
Block a user