mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS#8786:Update ROSA CLI guides with longer cluster name feature
This commit is contained in:
AedinC
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
146ef72e18
commit
6ea7cad646
@@ -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 \
|
||||
|
||||
@@ -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]
|
||||
|
||||
@@ -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]
|
||||
----
|
||||
|
||||
@@ -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]
|
||||
----
|
||||
|
||||
@@ -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`.
|
||||
|
||||
|
||||
@@ -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,7 +45,7 @@ $ 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_.
|
||||
+
|
||||
@@ -54,7 +53,6 @@ $ rosa create cluster --cluster-name=<cluster_name> \ <.>
|
||||
====
|
||||
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.
|
||||
|
||||
@@ -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[]
|
||||
@@ -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.
|
||||
+
|
||||
[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.
|
||||
====
|
||||
|
||||
<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[]
|
||||
--
|
||||
+
|
||||
. Check the status of your cluster:
|
||||
+
|
||||
[source,terminal]
|
||||
|
||||
@@ -219,63 +219,65 @@ $ rosa create cluster --interactive --sts
|
||||
I: Interactive mode enabled.
|
||||
Any optional fields can be left empty and a default will be selected.
|
||||
? Cluster name: <cluster_name>
|
||||
Deploy cluster with Hosted Control Plane (optional): No
|
||||
? Create cluster admin user: Yes <1>
|
||||
? Username: user-admin <1>
|
||||
? Password: [? for help] *************** <1>
|
||||
? OpenShift version: 4.15.0 <2>
|
||||
? Configure the use of IMDSv2 for ec2 instances optional/required (optional): <3>
|
||||
I: Using arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Installer-Role for the Installer role <4>
|
||||
? Domain prefix: <domain_prefix> <1>
|
||||
? Deploy cluster with Hosted Control Plane (optional): No
|
||||
? Create cluster admin user: Yes <2>
|
||||
? Username: user-admin <2>
|
||||
? Password: [? for help] *************** <2>
|
||||
? OpenShift version: 4.15.0 <3>
|
||||
? Configure the use of IMDSv2 for ec2 instances optional/required (optional): <4>
|
||||
I: Using arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Installer-Role for the Installer role <5>
|
||||
I: Using arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-ControlPlane-Role for the ControlPlane role
|
||||
I: Using arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Worker-Role for the Worker role
|
||||
I: Using arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Support-Role for the Support role
|
||||
? External ID (optional): <5>
|
||||
? Operator roles prefix: <cluster_name>-<random_string> <6>
|
||||
? External ID (optional): <6>
|
||||
? Operator roles prefix: <cluster_name>-<random_string> <7>
|
||||
? Deploy cluster using pre registered OIDC Configuration ID:
|
||||
? Tags (optional) <7>
|
||||
? Multiple availability zones (optional): No <8>
|
||||
? Tags (optional) <8>
|
||||
? Multiple availability zones (optional): No <9>
|
||||
? AWS region: us-east-1
|
||||
? PrivateLink cluster (optional): No
|
||||
? Install into an existing VPC (optional): Yes <9>
|
||||
? Install into an existing VPC (optional): Yes <10>
|
||||
? Select availability zones (optional): No
|
||||
? Enable Customer Managed key (optional): No <10>
|
||||
? Enable Customer Managed key (optional): No <11>
|
||||
? Compute nodes instance type (optional):
|
||||
? Enable autoscaling (optional): No
|
||||
? Compute nodes: 2
|
||||
? Additional Security Group IDs (optional): <11>
|
||||
? Additional Security Group IDs (optional): <12>
|
||||
? > [*] sg-0e375ff0ec4a6cfa2 ('sg-1')
|
||||
? > [ ] sg-0e525ef0ec4b2ada7 ('sg-2')
|
||||
? Machine CIDR: 10.0.0.0/16
|
||||
? Service CIDR: 172.30.0.0/16
|
||||
? Pod CIDR: 10.128.0.0/14
|
||||
? Host prefix: 23
|
||||
? Encrypt etcd data (optional): No <12>
|
||||
? Encrypt etcd data (optional): No <13>
|
||||
? Disable Workload monitoring (optional): No
|
||||
I: Creating cluster '<cluster_name>'
|
||||
I: To create this cluster again in the future, you can run:
|
||||
rosa create cluster --cluster-name <cluster_name> --role-arn arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Installer-Role --support-role-arn arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Support-Role --master-iam-role arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-ControlPlane-Role --worker-iam-role arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Worker-Role --operator-roles-prefix <cluster_name>-<random_string> --region us-east-1 --version 4.15.0 --additional-compute-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-infra-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-control-plane-security-group-ids sg-0e375ff0ec4a6cfa2 --replicas 2 --machine-cidr 10.0.0.0/16 --service-cidr 172.30.0.0/16 --pod-cidr 10.128.0.0/14 --host-prefix 23 <13>
|
||||
rosa create cluster --cluster-name <cluster_name> --role-arn arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Installer-Role --support-role-arn arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Support-Role --master-iam-role arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-ControlPlane-Role --worker-iam-role arn:aws:iam::<aws_account_id>:role/ManagedOpenShift-Worker-Role --operator-roles-prefix <cluster_name>-<random_string> --region us-east-1 --version 4.15.0 --additional-compute-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-infra-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-control-plane-security-group-ids sg-0e375ff0ec4a6cfa2 --replicas 2 --machine-cidr 10.0.0.0/16 --service-cidr 172.30.0.0/16 --pod-cidr 10.128.0.0/14 --host-prefix 23 <14>
|
||||
I: To view a list of clusters and their status, run 'rosa list clusters'
|
||||
I: Cluster '<cluster_name>' has been created.
|
||||
I: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.
|
||||
...
|
||||
----
|
||||
<1> When creating your cluster, you can create a local administrator user for your cluster. Selecting `Yes` then prompts you to create a user name and password for the cluster admin. The user name must not contain `/`, `:`, or `%`. The password must be at least 14 characters (ASCII-standard) without whitespaces. This process automatically configures an htpasswd identity provider.
|
||||
<2> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.15.0`.
|
||||
<3> Optional: Specify 'optional' to configure all EC2 instances to use both v1 and v2 endpoints of EC2 Instance Metadata Service (IMDS). This is the default value. Specify 'required' to configure all EC2 instances to use IMDSv2 only.
|
||||
<1> Optional. When creating your cluster, you can customize the subdomain for your cluster on `*.openshiftapps.com` using the `--domain-prefix` flag. The value for this flag must be unique within your organization, cannot be longer than 15 characters, and cannot be changed after cluster creation. If the flag 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.
|
||||
<2> When creating your cluster, you can create a local administrator user for your cluster. Selecting `Yes` then prompts you to create a user name and password for the cluster admin. The user name must not contain `/`, `:`, or `%`. The password must be at least 14 characters (ASCII-standard) without whitespaces. This process automatically configures an htpasswd identity provider.
|
||||
<3> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.15.0`.
|
||||
<4> Optional: Specify 'optional' to configure all EC2 instances to use both v1 and v2 endpoints of EC2 Instance Metadata Service (IMDS). This is the default value. Specify 'required' to configure all EC2 instances to use IMDSv2 only.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
The Instance Metadata Service settings cannot be changed after your cluster is created.
|
||||
====
|
||||
<4> If you have more than one set of account roles for your cluster version in your AWS account, an interactive list of options is provided.
|
||||
<5> Optional: Specify an unique identifier that is passed by {product-title} and the OpenShift installer when an account role is assumed. This option is only required for custom account roles that expect an external ID.
|
||||
<6> 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 _Defining an Operator IAM role prefix_.
|
||||
<5> If you have more than one set of account roles for your cluster version in your AWS account, an interactive list of options is provided.
|
||||
<6> Optional: Specify an unique identifier that is passed by {product-title} and the OpenShift installer when an account role is assumed. This option is only required for custom account roles that expect an external ID.
|
||||
<7> 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 _Defining an Operator IAM role prefix_.
|
||||
+
|
||||
[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.
|
||||
====
|
||||
<7> Optional: Specify a tag that is used on all resources created by {product-title} in AWS. Tags can help you manage, identify, organize, search for, and filter resources within AWS. Tags are comma separated, for example: "key value, foo bar".
|
||||
<8> Optional: Specify a tag that is used on all resources created by {product-title} in AWS. Tags can help you manage, identify, organize, search for, and filter resources within AWS. Tags are comma separated, for example: "key value, data input".
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
@@ -284,8 +286,8 @@ Tags that are added by Red Hat are required for clusters to stay in compliance w
|
||||
|
||||
{product-title} does not support adding additional tags outside of ROSA cluster-managed resources. These tags can be lost when AWS resources are managed by the ROSA cluster. In these cases, you might need custom solutions or tools to reconcile the tags and keep them intact.
|
||||
====
|
||||
<8> Optional: Multiple availability zones are recommended for production workloads. The default is a single availability zone.
|
||||
<9> Optional: You can create a cluster in an existing VPC, or ROSA can create a new VPC to use.
|
||||
<9> Optional: Multiple availability zones are recommended for production workloads. The default is a single availability zone.
|
||||
<10> Optional: You can create a cluster in an existing VPC, or ROSA can create a new VPC to use.
|
||||
+
|
||||
[WARNING]
|
||||
====
|
||||
@@ -293,7 +295,7 @@ You cannot install a ROSA cluster into an existing VPC that was created by the O
|
||||
|
||||
To verify whether a VPC was created by the OpenShift installer, check for the `owned` value on the `kubernetes.io/cluster/<infra-id>` tag. For example, when viewing the tags for the VPC named `mycluster-12abc-34def`, the `kubernetes.io/cluster/mycluster-12abc-34def` tag has a value of `owned`. Therefore, the VPC was created by the installer and must not be modified by the administrator.
|
||||
====
|
||||
<10> Optional: Enable this option if you are using your own AWS KMS key to encrypt the control plane, infrastructure, worker node root volumes, and PVs. Specify the ARN for the KMS key that you added to the account-wide role ARN in the preceding step.
|
||||
<11> Optional: Enable this option if you are using your own AWS KMS key to encrypt the control plane, infrastructure, worker node root volumes, and PVs. Specify the ARN for the KMS key that you added to the account-wide role ARN in the preceding step.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
@@ -302,15 +304,15 @@ Only persistent volumes (PVs) created from the default storage class are encrypt
|
||||
PVs created by using any other storage class are still encrypted, but the PVs are not encrypted with this key unless the storage class is specifically configured to use this key.
|
||||
====
|
||||
|
||||
<11> Optional: You can select additional custom security groups to use in your cluster. You must have already created the security groups and associated them with the VPC you selected for this cluster. You cannot add or edit security groups for the default machine pools after you create the machine pool. For more information, see the requirements for _Security groups_ under _Additional resources_.
|
||||
<12> Optional: Enable this option only if your use case requires etcd key value encryption in addition to the control plane storage encryption that encrypts the etcd volumes by default. With this option, the etcd key values are encrypted but not the keys.
|
||||
<12> Optional: You can select additional custom security groups to use in your cluster. You must have already created the security groups and associated them with the VPC you selected for this cluster. You cannot add or edit security groups for the default machine pools after you create the machine pool. For more information, see the requirements for _Security groups_ under _Additional resources_.
|
||||
<13> Optional: Enable this option only if your use case requires etcd key value encryption in addition to the control plane storage encryption that encrypts the etcd volumes by default. With this option, the etcd key values are encrypted but not the keys.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
By enabling etcd encryption for the key values in etcd, you will incur a performance overhead of approximately 20%. The overhead is a result of introducing this second layer of encryption, in addition to the default control plane storage encryption that encrypts the etcd volumes. Red Hat recommends that you enable etcd encryption only if you specifically require it for your use case.
|
||||
====
|
||||
+
|
||||
<13> The output includes a custom command that you can run to create a cluster with the same configuration in the future.
|
||||
<14> The output includes a custom command that you can run to create a cluster with the same configuration in the future.
|
||||
--
|
||||
+
|
||||
As an alternative to using the `--interactive` mode, you can specify the customization options directly when you run the `rosa create cluster` command. Run the `rosa create cluster --help` command to view a list of available CLI options, or see _create cluster_ in _Managing objects with the ROSA CLI_.
|
||||
|
||||
@@ -19,12 +19,11 @@ The following table describes the interactive cluster creation mode options:
|
||||
|`Cluster name`
|
||||
|Enter a name for your cluster, for example `my-rosa-cluster`.
|
||||
|
||||
|`Domain prefix`
|
||||
|Enter a name for the domain prefix for the subdomain of your cluster, for example `my-rosa-cluster`.
|
||||
|
||||
|`Deploy cluster with Hosted Control Plane (optional)`
|
||||
|Enable the use of Hosted Control Planes.
|
||||
[IMPORTANT]
|
||||
====
|
||||
The ROSA with Hosted Control Planes functionality is currently offered as a Technology Preview. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete.
|
||||
====
|
||||
|
||||
|`Create cluster admin user`
|
||||
|Create a cluster administrator user when you create your cluster using the htpasswd identity provider. The username must not contain `/`, `:`, or `%`. The password must be at least 14 characters (ASCII-standard) without whitespaces.
|
||||
|
||||
@@ -18,6 +18,8 @@ toc::[]
|
||||
|
||||
* **ROSA CLI update.** The ROSA CLI (`rosa`) was updated to a new version. For information about what has changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.37[ROSA CLI release notes]. For more information about the ROSA CLI (`rosa`), see xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-about_rosa-getting-started-cli[About the ROSA CLI].
|
||||
|
||||
* **Longer cluster names enhancement.** You can now specify a cluster name that is longer than 15 characters. For cluster names that are longer than 15 characters, you have the option to customize the domain prefix for the cluster URL by using the `domain-prefix` flag in the ROSA CLI (`rosa`). For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-create-cluster-command_rosa-managing-objects-cli[create cluster in Managing objects with the ROSA CLI].
|
||||
|
||||
* **Additional Security Groups for {hcp-title}.** Starting with ROSA CLI version 1.2.37, you can now use the `--additional-security-group-ids <sec_group_id>` when creating machine pools on {hcp-title} clusters. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.html#creating_machine_pools_cli_rosa-managing-worker-nodes[Creating a machine pool using the ROSA CLI] and the xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.html#rosa-create-machinepool_rosa-managing-objects-cli[create machinepool] section of the ROSA CLI reference.
|
||||
|
||||
[id="rosa-q1-2024_{context}"]
|
||||
@@ -41,6 +43,14 @@ For more information on region availabilities, see xref:../rosa_architecture/ros
|
||||
|
||||
* **Availability zone update.** You can now optionally select a single availability zone (AZ) for machine pools when you have a multi-AZ cluster. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_machine_pools_cli_rosa-managing-worker-nodes[Creating a machine pool using the ROSA CLI].
|
||||
|
||||
* **Log linking is enabled by default** - Beginning with {product-title} 4.15, log linking is enabled by default. Log linking gives you access to the container logs for your pods.
|
||||
|
||||
* **Availability zone update.** You can now optionally select a single availability zone (AZ) for machine pools when you have a multi-AZ cluster. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_machine_pools_cli_rosa-managing-worker-nodes[Creating a machine pool using the ROSA CLI].
|
||||
|
||||
* **Delete cluster command enhancement.** With the release of ROSA CLI (`rosa`) version 1.2.31, the `--best-effort` argument was added, which allows you to force-delete clusters when using the `rosa delete cluster` command. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-delete-cluster_rosa-managing-objects-cli[delete cluster].
|
||||
|
||||
* **ROSA CLI update.** The ROSA CLI (`rosa`) was updated to a new version. For information about what has changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.35[ROSA CLI release notes]. For more information about the ROSA CLI (`rosa`), see xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-about_rosa-getting-started-cli[About the ROSA CLI].
|
||||
|
||||
[id="rosa-q4-2023_{context}"]
|
||||
=== Q4 2023
|
||||
|
||||
|
||||
27
snippets/rosa-long-cluster-name.adoc
Normal file
27
snippets/rosa-long-cluster-name.adoc
Normal file
@@ -0,0 +1,27 @@
|
||||
|
||||
//This snippet appears in the following assemblies:
|
||||
//
|
||||
// * ../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-quickly.adoc
|
||||
// * ../rosa_install_access_delete_clusters/rosa-aws-privatelink-creating-cluster.adoc
|
||||
// * ../networking/rosa-shared-vpc-config.adoc
|
||||
// * ../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc
|
||||
// * ../monitoring/enabling-monitoring-for-user-defined-projects.adoc
|
||||
// * ../rosa_cluster_admin/rosa-cluster-autoscaling.adoc
|
||||
|
||||
//This snippet appears in the following modules:
|
||||
//
|
||||
// * ../rosa-sts-creating-a-cluster-quickly-cli.adoc
|
||||
// * ../rosa-aws-privatelink-create-cluster.adoc
|
||||
// * ../rosa-sharing-vpc-cluster-creation.adoc
|
||||
// * ../rosa-hcp-sts-creating-a-cluster-cli.adoc
|
||||
// * ../creating-cluster-with-aws-kms-key.adoc
|
||||
// * ../rosa-enable-cluster-autoscale-cli-interactive.adoc
|
||||
// * ../rosa_cluster_admin/rosa-cluster-autoscaling.adoc
|
||||
|
||||
:_mod-docs-content-type: SNIPPET
|
||||
[NOTE]
|
||||
====
|
||||
If your cluster name is longer than 15 characters, it will contain an autogenerated domain prefix as a sub-domain 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.
|
||||
====
|
||||
Reference in New Issue
Block a user