Merge pull request #72693 from AedinC/OSDOCS-8786

[OSDOCS#8786] Update CLI guides with new longer cluster name feature

Author: mburke5678

modules/creating-cluster-with-aws-kms-key.adoc

@@ -133,11 +133,14 @@ $ aws kms put-key-policy --key-id $KMS_ARN \
 ----
 
 . Create the cluster by running the following command:
-
++
+--
+include::snippets/rosa-long-cluster-name.adoc[]
+--
 +
 [source,terminal]
 ----
-$ rosa create cluster --cluster-name <cluster_name> \
+$ rosa create cluster --cluster-name <cluster_name> \ 
 --subnet-ids <private_subnet_id>,<public_subnet_id> \
 --sts \
 --mode auto \

modules/rosa-aws-privatelink-create-cluster.adoc

@@ -30,8 +30,11 @@ If you use a firewall, you must configure it so that {product-title} can access
 
 For more information, see the AWS PrivateLink firewall prerequisites section.
 ====
-
-
++
+--
+include::snippets/rosa-long-cluster-name.adoc[]
+--
++
 ** To create a Single-AZ cluster:
 +
 [source,terminal]

modules/rosa-cluster-autoscaler-cli-during.adoc

@@ -11,15 +11,17 @@ You can use the ROSA CLI (`rosa`) to set cluster-wide autoscaling behavior durin
 .Procedure
 
 - During cluster creation, type `--enable autoscaling` after the cluster name to enable machine autoscaling:
-+
+
+include::snippets/rosa-long-cluster-name.adoc[]
+
 .Example:
 [source,terminal]
 ----
 $ rosa create cluster --cluster-name <cluster_name> --enable-autoscaling
 ----
-+
+
 Set at least one parameter to enable cluster autoscaling by running the following command:
-+
+
 .Example:
 [source,terminal]
 ----

modules/rosa-cluster-autoscaler-cli-interactive-during.adoc

@@ -19,9 +19,10 @@ Interactive mode provides more information about available configurable paramete
 ----
 $ rosa create cluster --cluster-name <cluster_name> --enable-autoscaling --interactive
 ----
-+
+include::snippets/rosa-long-cluster-name.adoc[]
+
 When the following prompt appears, enter *y* to go through all available autoscaling options.
-+
+
 .Example interactive prompt:
 [source,terminal]
 ----

modules/rosa-create-objects.adoc

@@ -126,7 +126,7 @@ $ rosa create cluster --cluster-name=<cluster_name> [arguments]
 |The identifier of one or more additional security groups to use along with the default security groups that are used with the control plane nodes created alongside the cluster. For more information on additional security groups, see the requirements for _Security groups_ under _Additional resources_.
 
 a|--cluster-name <cluster_name>
-|Required. The name of the cluster. When used with the `create cluster` command, this argument is used to set the cluster name and to generate a sub-domain for your cluster on `openshiftapps.com`. The value for this argument must be unique within your organization.
+|Required. The name of the cluster. When used with the `create cluster` command, this argument is used to set the cluster name and can hold up to 54 characters. The value for this argument must be unique within your organization.
 
 |--compute-machine-type <instance_type>
 |The instance type for compute nodes in the cluster. This determines the amount of memory and vCPU that is allocated to each compute node. For more information on valid instance types, see _AWS Instance types_ in _ROSA service definition_.
@@ -140,6 +140,10 @@ a|--cluster-name <cluster_name>
 |--dry-run
 |Simulates creating the cluster.
 
+|--domain-prefix
+|Optional: When used with the `create cluster` command, this argument sets the subdomain for your cluster on `*.openshiftapps.com`. The value for this argument must be unique within your organization, cannot be longer than 15 characters, and cannot be changed after cluster creation.
+If the argument is not supplied, an autogenerated value is created that depends on the length of the cluster name. If the cluster name is fewer than or equal to 15 characters, that name is used for the domain prefix. If the cluster name is longer than 15 characters, the domain prefix is randomly generated to a 15 character string.
+
 |--ec2-metadata-http-tokens string
 |Configures the use of IMDSv2 for EC2 instances. Valid values are `optional` (default) or `required`.
 

modules/rosa-hcp-sts-creating-a-cluster-cli.adoc

@@ -35,7 +35,6 @@ When using the {product-title} (ROSA) CLI, `rosa`, to create a cluster, you can
 When creating a {hcp-title} cluster, the default machine Classless Inter-Domain Routing (CIDR) is `10.0.0.0/16`. If this does not correspond to the CIDR range for your VPC subnets, add `--machine-cidr <address_block>` to the following commands. To learn more about the default CIDR ranges for {product-title}, see xref:../networking/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions].
 ====
 +
---
 * If you did not set environmental variables, run the following command:
 +
 [source,terminal]
@@ -46,15 +45,14 @@ $ rosa create cluster --cluster-name=<cluster_name> \ <.>
     --oidc-config-id <id-of-oidc-configuration> \ 
     --subnet-ids=<public-subnet-id>,<private-subnet-id>
 ----
-<.> Specify the name of your cluster, ensuring that the cluster name consists of no more than 15 lowercase alphanumeric characters or '-', starts with a letter, and ends with an alphanumeric character.
+<.> Specify the name of your cluster. If your cluster name is longer than 15 characters, it will contain an autogenerated domain prefix as a subdomain for your provisioned cluster on openshiftapps.com. To customize the subdomain, use the `--domain-prefix` flag. The domain prefix cannot be longer than 15 characters, must be unique, and cannot be changed after cluster creation.
 <.> Optional: The `--private` argument is used to create private {hcp-title} clusters. If you use this argument, ensure that you only use your private subnet ID for `--subnet-ids`.
 <.> By default, the cluster-specific Operator role names are prefixed with the cluster name and a random 4-digit hash. You can optionally specify a custom prefix to replace `<cluster_name>-<hash>` in the role names. The prefix is applied when you create the cluster-specific Operator IAM roles. For information about the prefix, see _About custom Operator IAM role prefixes_.
 +
 [NOTE]
 ====
 If you specified custom ARN paths when you created the associated account-wide roles, the custom path is automatically detected. The custom path is applied to the cluster-specific Operator roles when you create them in a later step.
 ====
---
 +
 * If you set the environmental variables, create a cluster with a single, initial machine pool, using either a publicly or privately available API, and a publicly or privately available Ingress by running the following command:
 +
@@ -71,7 +69,7 @@ $ rosa create cluster --private --cluster-name=<cluster_name> \
 ----
 $ rosa create cluster --cluster-name=<cluster_name> --mode=auto --hosted-cp --operator-roles-prefix=$OPERATOR_ROLES_PREFIX --oidc-config-id=$ODIC_CONFIG --subnet-ids=$SUBNET_IDS
 ----
-
++
 . Check the status of your cluster by running the following command:
 +
 [source,terminal]
@@ -90,11 +88,11 @@ The following `State` field changes are listed in the output as the cluster inst
 ====
 If the installation fails or the `State` field does not change to `ready` after more than 10 minutes, check the installation troubleshooting documentation for details. For more information, see _Troubleshooting installations_. For steps to contact Red Hat Support for assistance, see _Getting support for Red Hat OpenShift Service on AWS_.
 ====
-
++
 . Track the progress of the cluster creation by watching the {product-title} installation program logs. To check the logs, run the following command:
 +
 [source,terminal]
 ----
-$ rosa logs install --cluster=<cluster_name> --watch \ <1>
+$ rosa logs install --cluster=<cluster_name> --watch \ <.>
 ----
-<1> Optional: To watch for new log messages as the installation progresses, use the `--watch` argument.
+<.> Optional: To watch for new log messages as the installation progresses, use the `--watch` argument.

modules/rosa-sharing-vpc-cluster-creation.adoc

@@ -25,4 +25,6 @@ image::372_OpenShift_on_AWS_persona_worflows_0923_4.png[]
 [source,terminal]
 ----
 rosa create cluster --cluster-name <cluster_name> --sts --operator-roles-prefix <prefix> --oidc-config-id <oidc_config_id> --region us-east-1 --subnet-ids <subnet_ids> --private-hosted-zone-id <hosted_zone_ID> --shared-vpc-role-arn <vpc-role-arn> --base-domain <dns-domain>
-----
+----
++
+include::snippets/rosa-long-cluster-name.adoc[]

modules/rosa-sts-creating-a-cluster-quickly-cli.adoc

@@ -39,20 +39,21 @@ $ rosa create account-roles --mode auto
 ====
 When using `auto` mode, you can optionally specify the `-y` argument to bypass the interactive prompts and automatically confirm operations.
 ====
-
++
 . Create a cluster with STS using the defaults. When you use the defaults, the latest stable OpenShift version is installed:
 +
+--
 [source,terminal]
 ----
-$ rosa create cluster --cluster-name <cluster_name> --sts --mode auto <1>
+$ rosa create cluster --cluster-name <cluster_name> \ <1>
+--sts --mode auto <2>
 ----
+
 <1> Replace `<cluster_name>` with the name of your cluster.
+<2> When you specify `--mode auto`, the `rosa create cluster` command creates the cluster-specific Operator IAM roles and the OIDC provider automatically. The Operators use the OIDC provider to authenticate.
+include::snippets/rosa-long-cluster-name.adoc[]
+--
 +
-[NOTE]
-====
-When you specify `--mode auto`, the `rosa create cluster` command creates the cluster-specific Operator IAM roles and the OIDC provider automatically. The Operators use the OIDC provider to authenticate.
-====
-
 . Check the status of your cluster:
 +
 [source,terminal]