You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/rosa-sts-cluster-terraform-setup.adoc
+1-8Lines changed: 1 addition & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,7 @@ endif::[]
14
14
[id="rosa-sts-cluster-terraform-setup_{context}"]
15
15
= Preparing your environment for Terraform
16
16
17
-
Before you can create your
18
-
ifdef::tf-classic-defaults[]
19
-
{rosa-classic-short}
20
-
endif::tf-classic-defaults[]
21
-
ifdef::tf-hcp-defaults[]
22
-
{rosa-short}
23
-
endif::tf-hcp-defaults[]
24
-
cluster by using Terraform, you need to export your link:https://console.redhat.com/openshift/token[offline {cluster-manager-first} token].
17
+
Before you can create your {product-title} cluster by using Terraform, you need to export your link:https://console.redhat.com/openshift/token[offline {cluster-manager-first} token].
25
18
26
19
.Procedure
27
20
. *Optional*: Because the Terraform files get created in your current directory during this procedure, you can create a new directory to store these files and navigate into it by running the following command:
Copy file name to clipboardExpand all lines: modules/rosa-sts-terraform-prerequisites.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
9
9
To use link:https://registry.terraform.io/providers/terraform-redhat/rhcs/latest/docs[the Red{nbsp}Hat Cloud Services provider] inside your Terraform configuration, you must meet the following prerequisites:
10
10
11
-
* You have installed the {product-title}(ROSA) command-line interface (CLI) tool.
11
+
* You have installed the {product-title} command-line interface (CLI) tool.
12
12
* You have your offline link:https://console.redhat.com/openshift/token/rosa[{cluster-manager-first} token].
13
13
* You have installed link:https://developer.hashicorp.com/terraform/downloads[Terraform version 1.4.6] or newer.
14
14
* You have created your AWS account-wide IAM roles.
You can use your own Container Network Interface (CNI) plugin when creating a
11
-
ifdef::openshift-rosa[]
12
-
{rosa-title}
13
-
endif::openshift-rosa[]
14
-
ifdef::openshift-rosa-hcp[]
15
-
{product-title}
16
-
endif::openshift-rosa-hcp[]
17
-
cluster. You can create a {rosa-short} cluster without a CNI and install your own CNI plugin after cluster creation.
10
+
You can use your own Container Network Interface (CNI) plugin when creating a {product-title} cluster. You can create a {product-title} cluster without a CNI and install your own CNI plugin after cluster creation.
18
11
19
12
[IMPORTANT]
20
13
====
21
14
For customers who choose to use their own CNI, the responsibility of CNI plugin support belongs to the customer in coordination with their chosen CNI vendor.
22
15
====
23
16
24
-
The default plugin for {rosa-short} is the xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin]. This plugin is the only Red Hat supported CNI plugin for {rosa-short}.
17
+
The default plugin for {product-title} is the xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin]. This plugin is the only Red Hat supported CNI plugin for {product-title}.
25
18
26
-
If you choose to use your own CNI for {rosa-short} clusters, it is strongly recommended that you obtain commercial support from the plugin vendor before creating your clusters. Red Hat support cannot assist with CNI-related issues such as pod to pod traffic for customers who choose to use their own CNI. Red Hat still provides support for all non-CNI issues. If you want CNI-related support from Red Hat, you must install the cluster with the default OVN-Kubernetes network plugin. For more information, see the xref:../rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc#rosa-policy-responsibility-matrix[responsibility matrix].
19
+
If you choose to use your own CNI for {product-title} clusters, it is strongly recommended that you obtain commercial support from the plugin vendor before creating your clusters. Red Hat support cannot assist with CNI-related issues such as pod to pod traffic for customers who choose to use their own CNI. Red Hat still provides support for all non-CNI issues. If you want CNI-related support from Red Hat, you must install the cluster with the default OVN-Kubernetes network plugin. For more information, see the xref:../rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc#rosa-policy-responsibility-matrix[responsibility matrix].
27
20
28
21
[id="rosa-hcp-no-cni-cluster-creation"]
29
-
== Creating a {rosa-short} cluster without a CNI plugin
22
+
== Creating a {product-title} cluster without a CNI plugin
30
23
31
24
=== Prerequisites
32
25
* Ensure that you have completed the xref:../rosa_planning/rosa-hcp-aws-prereqs.adoc#rosa-hcp-aws-prereqs[AWS prerequisites].
If you want to delete a {rosa-title} cluster, you can use either the {cluster-manager-first} or the ROSA command-line interface (CLI) (`rosa`). After deleting your cluster, you can also delete the AWS Identity and Access Management (IAM) resources that are used by the cluster.
9
+
If you want to delete a {product-title} cluster, you can use either the {cluster-manager-first} or the ROSA command-line interface (CLI) (`rosa`). After deleting your cluster, you can also delete the AWS Identity and Access Management (IAM) resources that are used by the cluster.
Creating {rosa-title} with {egress-zero} provides a way to enhance your cluster's stability and security by allowing your cluster to use the image registry in the local region if the cluster cannot access the internet. Your cluster first tries to pull the images from Quay, and when they aren't reached, it instead pulls the images from the image registry in the local region.
8
+
Creating {product-title} with {egress-zero} provides a way to enhance your cluster's stability and security by allowing your cluster to use the image registry in the local region if the cluster cannot access the internet. Your cluster first tries to pull the images from Quay, and when they aren't reached, it instead pulls the images from the image registry in the local region.
9
9
10
10
All public and private clusters with {egress-zero} get their Red{nbsp}Hat container images from an Amazon Elastic Container Registry (ECR) located in the local region of the cluster instead of gathering these images from various endpoints and registries on the internet. ECR provides storage for OpenShift release images as well as Red{nbsp}Hat Operators. All requests for ECR are kept within your AWS network by serving them over a VPC endpoint within your cluster.
11
11
12
12
{egress-zero-title} use AWS ECR to provision your clusters without the need for public internet. Because necessary cluster lifecycle processes occur over AWS private networking, AWS ECR serves as a critical service for core cluster platform images. For more information on AWS ECR, see link:https://aws.amazon.com/ecr/[Amazon Elastic Container Registry].
13
13
14
14
You can create a fully operational cluster that does not require a public egress by configuring a virtual private cloud (VPC) and using the `--properties zero_egress:true` flag when creating your cluster.
15
15
16
-
See xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {rosa-short} clusters] to upgrade clusters using {egress-zero}.
16
+
See xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {product-title} clusters] to upgrade clusters using {egress-zero}.
17
17
18
18
[NOTE]
19
19
====
@@ -62,17 +62,17 @@ A physical connection might exist between machines on the internal network and a
62
62
63
63
[IMPORTANT]
64
64
====
65
-
* You can use {egress-zero} on all supported versions of {rosa-short} that use the hosted control plane architecture; however, Red{nbsp}Hat suggests using the latest available z-stream release for each {ocp} version.
65
+
* You can use {egress-zero} on all supported versions of {product-title} that use the hosted control plane architecture; however, Red{nbsp}Hat suggests using the latest available z-stream release for each {ocp} version.
66
66
67
67
* While you may install and upgrade your clusters as you would a regular cluster, due to an upstream issue with how the internal image registry functions in disconnected environments, your cluster that uses {egress-zero} will not be able to fully use all platform components, such as the image registry. You can restore these features by using the latest ROSA version when upgrading or installing your cluster.
== Creating a Virtual Private Cloud for your {hcp-title} clusters
73
+
== Creating a Virtual Private Cloud for your {product-title} clusters
74
74
75
-
You must have a Virtual Private Cloud (VPC) to create a {rosa-short} cluster. To pull images from the local ECR mirror over your VPC endpoint, you must configure a privatelink service connection and modify the default security groups with specific tags. Use one of the following methods to create a VPC:
75
+
You must have a Virtual Private Cloud (VPC) to create a {product-title} cluster. To pull images from the local ECR mirror over your VPC endpoint, you must configure a privatelink service connection and modify the default security groups with specific tags. Use one of the following methods to create a VPC:
76
76
77
77
* Create a VPC using the ROSA command-line interface (CLI)
cluster using the command-line interface (CLI), grant user access, deploy your first application, and learn how to revoke user access and delete your cluster.
9
+
Follow this guide to quickly create a {product-title} cluster using the command-line interface (CLI), grant user access, deploy your first application, and learn how to revoke user access and delete your cluster.
Before you can use the {hybrid-console} to deploy {rosa-short} clusters, you must associate your AWS account with your Red{nbsp}Hat organization and create the required account-wide AWS IAM STS roles and policies for ROSA.
22
+
Before you can use the {hybrid-console} to deploy {product-title} clusters, you must associate your AWS account with your Red{nbsp}Hat organization and create the required account-wide AWS IAM STS roles and policies for ROSA.
0 commit comments