mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
376 lines
41 KiB
Plaintext
376 lines
41 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="rosa-whats-new"]
|
|
= What's new with {product-title}
|
|
include::_attributes/common-attributes.adoc[]
|
|
include::_attributes/attributes-openshift-dedicated.adoc[]
|
|
:context: rosa-whats-new
|
|
|
|
toc::[]
|
|
|
|
{product-title} is a fully-managed, turnkey application platform that allows you to focus on delivering value to your customers by building and deploying applications. Red{nbsp}Hat and AWS site reliability engineering (SRE) experts manage the underlying platform so you do not have to worry about the complexity of infrastructure management. {product-title} provides seamless integration with a wide range of AWS compute, database, analytics, machine learning, networking, mobile, and other services to further accelerate the building and delivering of differentiating experiences to your customers.
|
|
|
|
{product-title} clusters are available on the {hybrid-console-url}. With the Red{nbsp}Hat {cluster-manager} application for {product-title}, you can deploy {product-title} clusters to cloud environments.
|
|
|
|
[id="rosa-new-changes-and-updates_{context}"]
|
|
== New changes and updates
|
|
[id="rosa-q3-2025_{context}"]
|
|
=== Q3 2025
|
|
ifdef::openshift-rosa-hcp[]
|
|
* ** New cluster deletion policy.**
|
|
{product-title} clusters now have a new deletion policy. This policy is based on a set time period of customer non-response to service notifications. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc#rosa-delete-policy_rosa-hcp-life-cycle[Deletion policy]. For specific revised terms and conditions, refer to link:https://www.redhat.com/licenses/Appendix-4-Red-Hat-Online-Services-20250805.pdf[Product Appendix 4].
|
|
|
|
* **Shared VPC for ROSA with HCP clusters.** You can create {product-title} clusters in shared, centrally-managed AWS virtual private clouds (VPCs). For more information, see xref:../rosa_hcp/rosa-hcp-shared-vpc-config.adoc#rosa-hcp-shared-vpc-config[Configuring a shared VPC for ROSA with HCP clusters].
|
|
|
|
* **Deprecated `--private-link` flags for {product-title} clusters**. Architectural changes to the ROSA CLI 1.2.55 make networking more flexible for {product-title} clusters. The `--private-link` flag previously used when creating a {product-title} cluster is now deprecated in favor of the `--private` and `--default-ingress-private` flags. Now, users can choose to have a combination of a public or private API with a public or private ingress. For more information, see xref:../rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc#rosa-hcp-aws-private-create-cluster_rosa-hcp-aws-private-creating-cluster[Creating a private cluster on {product-title}].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **Changed default ingress listening method to begin with Day 1 operations**. Previously, the default ingress listening method was a Day 2 operation. Now, the default ingress listening method is a Day 1 operation.
|
|
|
|
[id="rosa-q2-2025_{context}"]
|
|
=== Q2 2025
|
|
|
|
// * **{product-title} SDN network plugin blocks future major upgrades**
|
|
* **Updated version requirements for migration from OpenShift SDN to OVN-Kubernetes.**
|
|
Your cluster version must be 4.16.43 or above to initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
|
|
+
|
|
If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to future major versions of {product-title} without migrating to OVN-Kubernetes.
|
|
//This link is broken. Commenting out until issues with Networking book have been resolved.
|
|
//ifdef::openshift-rosa[]
|
|
//+
|
|
//For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
|
|
//endif::openshift-rosa[]
|
|
//remove conditional when networking book is merged
|
|
|
|
ifdef::openshift-rosa[]
|
|
+
|
|
For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
|
|
endif::openshift-rosa[]
|
|
|
|
* **AWS Trainium and Inferentia instance types now supported.** You can now use {AWS} Trainium and Inferentia instance types for your {product-title} clusters. For more information, see
|
|
ifdef::openshift-rosa[]
|
|
xref:../rosa_architecture/rosa_policy_service_definition/rosa-instance-types.adoc#rosa-instance-types[{product-title} instance types].
|
|
endif::openshift-rosa[]
|
|
ifdef::openshift-rosa-hcp[]
|
|
xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-hcp-instance-types[{product-title} instance types].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **New version of {product-title} available.** {product-title} version 4.19 is now available for new clusters.
|
|
// re-add once upgrade to 4.19 is available
|
|
// For more information about upgrading to this latest version, see xref:../upgrading/rosa-upgrading-sts.adoc#rosa-upgrading-sts[Upgrading ROSA (classic architecture) clusters].
|
|
endif::openshift-rosa[]
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **New version of {product-title} available.** {product-title} version 4.19 is now available for new clusters.
|
|
// re-add once upgrade to 4.19 is available
|
|
// For more information about upgrading to this latest version, see xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {hcp-title} clusters].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **{product-title} cluster ownership transfer is now available for {product-title}.** You can now transfer ownership of {product-title} clusters. For more information, see link:https://docs.redhat.com/en/documentation/openshift_cluster_manager/1-latest/html/managing_clusters/assembly-managing-clusters#initiating-rosa-classic-ownership-transfer-proc_downloading-and-updating-pull-secrets[Initiating ownership transfer of a {product-title} cluster].
|
|
endif::openshift-rosa[]
|
|
|
|
[id="rosa-q1-2025_{context}"]
|
|
=== Q1 2025
|
|
|
|
//Commented out until rosa-cluster-autoscaling-hcp file has been added to hcp topic map.
|
|
//* **Cluster autoscaling is now available for {product-title}.** You can configure cluster autoscaling for {product-title}. For more information, see xref:../rosa_cluster_admin/rosa-cluster-autoscaling-hcp.adoc#rosa-cluster-autoscaling-hcp[Cluster autoscaling].
|
|
//endif::openshift-rosa-hcp[]
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **{product-title} region added.** {product-title} is now available in the following regions:
|
|
+
|
|
** Tel Aviv (`il-central-1`)
|
|
** Calgary (`ca-west-1`)
|
|
+
|
|
For more information on region availabilities, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
|
|
endif::openshift-rosa[]
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **{product-title} region added.** {product-title} is now available in the following regions:
|
|
+
|
|
** Malaysia (`ap-southeast-5`)
|
|
** Tel Aviv (`il-central-1`)
|
|
** Calgary (`ca-west-1`)
|
|
+
|
|
For more information on region availabilities, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-hcp-service-definition[Regions and availability zones].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **Cluster autoscaling is now available for {product-title}.** You can configure cluster autoscaling for {product-title}. For more information, see xref:../rosa_cluster_admin/rosa-cluster-autoscaling.adoc#rosa-cluster-autoscaling[Cluster autoscaling].
|
|
|
|
* **New version of {product-title} available.** {product-title} version 4.18 is now available. For more information about upgrading to this latest version, see xref:../upgrading/rosa-upgrading-sts.adoc#rosa-upgrading-sts[Upgrading {product-title} clusters].
|
|
endif::openshift-rosa[]
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **New version of {product-title} available.** {product-title} version 4.18 is now available. For more information about upgrading to this latest version, see xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {product-title} clusters].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **Graphical installer enhancements.** You can now use the graphical installer in {hybrid-console} to configure the following options when you create your cluster:
|
|
** Configure a `cluster-admin` user and optionally define a custom password.
|
|
** Configure the root disk size for the default machine pool.
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Image configuration is now available for {product-title}.** You can configure registries within a cluster to exclude some registries or allow only a defined list. It also allows to expose additional trusted bundle for registries to pull from. For more information, see xref:../openshift_images/image-configuration-hcp.adoc#images-configuration-parameters-hcp_image-configuration-hcp[Image configuration resources for {product-title}].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **{product-title} cluster node limit update.** {product-title} clusters versions 4.14.14 and greater can now scale to 249 worker nodes. This is an increase from the previous limit of 180 nodes.
|
|
endif::openshift-rosa[]
|
|
// Removed as part of OSDOCS-13310, until figures are verified.
|
|
//For more information, see xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability].
|
|
|
|
// commented out as seems to be duplicated below
|
|
//ifdef::openshift-rosa-hcp[]
|
|
//* **Egress zero is now generally available on {product-title} clusters.** 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. For more information, see xref:../rosa_hcp/rosa-hcp-egress-zero-install.adoc#rosa-hcp-egress-zero-install[Creating a {egress-zero-title}].
|
|
//endif::openshift-rosa-hcp[]
|
|
|
|
//Commenting this out as is repeated above, although version type is slightly different.Out of scope for Whats new pruning task. Will investigate separately.
|
|
//* **{product-title} SDN network plugin blocks future major upgrades**
|
|
//* **Initiate live migration from OpenShift SDN to OVN-Kubernetes.**
|
|
//As part of the {product-title} move to OVN-Kubernetes as the only supported network plugin starting with {product-title} version 4.17, users can now initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
|
|
//+
|
|
//If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to future major versions of {product-title} without migrating to OVN-Kubernetes.
|
|
//+
|
|
//For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **Red{nbsp}Hat SRE log-based alerting endpoints have been updated.** {product-title} customers who are using a firewall to control egress traffic can now remove all references to `*.osdsecuritylogs.splunkcloud.com:9997` from your firewall allowlist. {product-title} clusters still require the `http-inputs-osdsecuritylogs.splunkcloud.com:443` log-based alerting endpoint to be accessible from the cluster.
|
|
endif::openshift-rosa[]
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **{product-title} now creates independent security groups for the AWS PrivateLink endpoint and worker nodes.** {product-title} clusters version 4.17.2 and greater can now add additional AWS security groups to the AWS PrivateLink endpoint to allow additional ingress traffic to the cluster's API. For more information, see xref:../rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc#rosa-hcp-aws-private-security-groups_rosa-hcp-aws-private-creating-cluster[Adding additional AWS security groups to the AWS PrivateLink endpoint].
|
|
|
|
* **Egress zero is now generally available on {product-title} clusters.** 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. For more information, see xref:../rosa_hcp/rosa-hcp-egress-zero-install.adoc#rosa-hcp-egress-zero-install[Creating a {egress-zero-title}].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
//Added back in HCP related content as part of Whats new pruning task.
|
|
|
|
[id="rosa-q4-2024_{context}"]
|
|
=== Q4 2024
|
|
ifdef::openshift-rosa[]
|
|
* **Learning tutorials for {product-title} cluster and application deployment.** You can now use the xref:../cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-deploying/cloud-experts-getting-started-choose-deployment-method.adoc#cloud-experts-getting-started-choose-deployment-method[Getting started with {product-title}] tutorials to quickly deploy a {product-title} cluster for demo or learning purposes. You can also use the xref:../cloud_experts_tutorials/cloud-experts-deploying-application/cloud-experts-deploying-application-intro.adoc#cloud-experts-deploying-application-intro[Deploying an application] tutorials to deploy an application on your demo cluster.
|
|
endif::openshift-rosa[]
|
|
|
|
* **Create a VPC using the ROSA CLI.** The `rosa create network` command lets you use the ROSA CLI to create a VPC for your cluster based on an AWS CloudFormation template. You can use this command to create and configure a VPC before creating your cluster. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-create-network_rosa-managing-objects-cli[create network].
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Create additional security groups in {product-title} clusters.** Starting with ROSA CLI version 1.2.47, you can now create additional security groups using the ROSA CLI when creating {product-title} clusters. Note that additional security group IDs attached to the machine pool cannot be modified. To remove or add more security group IDs, replace the entire machine pool with a new one.
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **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/[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].
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **`VolumeDetachTimeout` configuration applied to machine pools for {product-title}.** {product-title} is applying a `VolumeDetachTimeout` configuration of 5 minutes to all machine pools. This prevents issues with node deletion when volumes fail to detach.
|
|
|
|
* **Configure machine pool disk volume for {product-title} clusters.** You can now configure the disk volume size for machine pools in {product-title} clusters. The default disk size is 300 GiB, and you can configure it from a minimum of 75 GiB to a maximum of 16,384 GiB. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#configuring-machine-pool-disk-volume_rosa-managing-worker-nodes[Configuring machine pool disk volume].
|
|
|
|
* **Edit the billing account for existing {product-title} clusters.** You can now update the billing account associated with your {product-title} clusters after cluster creation. For more information, see the {cluster-manager} documentation: link:https://docs.redhat.com/en/documentation/openshift_cluster_manager/1-latest/html-single/managing_clusters/index#proc_updating-billing-accts-rosa-hcp_assembly-managing-clusters[Updating billing accounts for OpenShift Service on AWS Hosted Control Planes clusters].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
[id="rosa-q3-2024_{context}"]
|
|
=== Q3 2024
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **{product-title} multi-architecture cluster update.** {product-title} clusters created before 25 July, 2024 will migrate to a multi-architecture image on their next upgrade allowing you to use {AWS} Arm-based Graviton instance types for your workloads. For more information, see xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-upgrade-options_rosa-hcp-upgrading[Upgrading {hcp-title} clusters].
|
|
|
|
* **{product-title} cluster node limit update.** {product-title} clusters can now scale to 500 worker nodes. This is an increase from the previous limit of 250 nodes. The 250 node limit is an increase from the previous limit 90 nodes on 26 August, 2024.
|
|
// Removed as part of OSDOCS-13310, until figures are verified.
|
|
// For more information, see xref:../rosa_planning/rosa-hcp-limits-scalability.adoc#tested-cluster-maximums-hcp-sd_rosa-hcp-limits-scalability[ROSA with HCP cluster maximums].
|
|
|
|
* **IMDSv2 support in {product-title}.** You can now enforce the use of the IMDSv2 endpoint for default machine pool worker nodes on new {product-title} clusters and for new machine pools on existing clusters. For more information, see xref:../rosa_hcp/terraform/rosa-hcp-creating-a-cluster-quickly-terraform.adoc#rosa-hcp-creating-a-cluster-quickly-terraform[Creating a default {product-title} cluster using Terraform].
|
|
|
|
* **Upgrade multiple nodes simultaneously.** You can now configure a machine pool to upgrade multiple nodes simultaneously. Two new machine pool parameters, `max-surge` and `max-unavailable`, give you greater control over how machine pool upgrades occur. For more information, see xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {product-title} clusters].
|
|
|
|
* **{product-title} Graviton Arm-based instance types.** You can now use {AWS} Arm-based Graviton instance types for your workloads in {product-title} clusters created after 24 July, 2024. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-sdpolicy-aws-instance-types-graviton_rosa-hcp-instance-types[AWS Graviton Arm-based instance types].
|
|
endif::openshift-rosa-hcp[]
|
|
// ifdef::openshift-rosa-hcp[]
|
|
// * **Upgrade multiple nodes simultaneously.** You can now configure a machine pool to upgrade multiple nodes simultaneously. Two new machine pool parameters, `max-surge` and `max-unavailable`, give you greater control over how machine pool upgrades occur. For more information, see xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {hcp-title} clusters].
|
|
// endif::openshift-rosa-hcp[]
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **{hcp-title} Graviton Arm-based instance types.** You can now use {AWS} Arm-based Graviton instance types for your workloads in {hcp-title-first} clusters created after 24 July, 2024. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-sdpolicy-aws-instance-types-graviton_rosa-hcp-instance-types[AWS Graviton Arm-based instance types].
|
|
endif::openshift-rosa-hcp[]
|
|
* **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.42[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-q2-2024_{context}"]
|
|
=== Q2 2024
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Approve additional principals for {product-title} clusters.** You can approve additional user-roles to connect to your cluster's private API server endpoint. For more information, see xref:../rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc#rosa-additional-principals-overview_rosa-hcp-aws-private-creating-cluster[Additional principals on your {product-title} cluster].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **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.41[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].
|
|
|
|
* **Approved Access for {product-title} clusters.** Red{nbsp}Hat Site Reliability Engineering (SRE) managing and proactively supporting ROSA Clusters will typically not require elevated access to customer clusters as part of the normal operations. In the unlikely event should Red{nbsp}Hat SRE (Site Reliability Engineer) need elevated access, the _Approved Access_ functionality provides an interface for customers to review and _approve_ or _deny_ access requests.
|
|
+
|
|
Elevated access requests to ROSA clusters and the corresponding cloud accounts can be created by Red{nbsp}Hat SRE either in response to a customer-initiated support ticket or in response to alerts received by a Red{nbsp}Hat SRE, as part of the standard incident response process. For more information, see xref:../support/approved-access.adoc#approved-access[Approved Access].
|
|
|
|
* **`rosa` command enhancement.** The `rosa describe` command has a new optional argument, `--get-role-policy-bindings`. This new argument allows users to view the policies attached to STS roles assigned to the selected cluster. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-describe-cluster_rosa-managing-objects-cli[describe cluster].
|
|
|
|
* **Expanded customer-managed policy capabilities.** You can now attach customer-managed policies to the IAM roles required to run {product-title} clusters. Furthermore, these customer-managed policies, including the permissions attached to those policies, are not modified during cluster or role upgrades. For more information, see xref:../rosa_architecture/rosa-sts-about-iam-resources.adoc#rosa-aws-customer-managed-policies_rosa-sts-about-iam-resources[Customer-managed policies].
|
|
|
|
ifdef::openshift-rosa[]
|
|
* **Permission boundaries for the installer role policy.** You can apply a policy as a _permissions boundary_ on the {product-title} installer role. The combination of policy and boundary policy limits the maximum permissions for the Amazon Web Services(AWS) Identity and Access Management (IAM) entity role. {product-title} includes a set of three prepared permission boundary policy files, with which you can restrict permissions for the installer role since changing the installer policy itself is not supported. For more information, see xref:../rosa_architecture/rosa-sts-about-iam-resources.adoc#rosa-sts-aws-requirements-attaching-boundary-policy_rosa-sts-about-iam-resources[Permission boundaries for the installer role].
|
|
|
|
* **Cluster delete protection.** You can now enable the cluster delete protection option, which helps to prevent you from accidentally deleting a cluster. For more information on using the cluster delete protection option with the ROSA CLI, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-edit-cluster_rosa-managing-objects-cli[edit cluster]. For more information on using the cluster delete protection option in the UI, see xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-quickly.adoc#rosa-sts-creating-a-cluster-using-defaults-ocm_rosa-sts-creating-a-cluster-quickly[Creating a cluster with the default options using OpenShift Cluster Manager].
|
|
endif::openshift-rosa[]
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **{product-title} regions added.** {product-title} is now available in the following regions:
|
|
+
|
|
** Zurich (`eu-central-2`)
|
|
** Hong Kong (`ap-east-1`)
|
|
** Osaka (`ap-northeast-3`)
|
|
** Spain (`eu-south-2`)
|
|
** UAE (`me-central-1`)
|
|
+
|
|
For more information on region availabilities, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-hcp-service-definition[Regions and availability zones].
|
|
|
|
* **Added support for external authentication providers.** You can now create clusters configured with external authentication providers, such as Microsoft Entra ID and KeyCloak. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc#rosa-hcp-sts-creating-a-cluster-ext-auth[Creating {product-title} clusters with external authentication].
|
|
|
|
* **Added support for external authentication providers.** You can now create clusters configured with external authentication providers, such as Microsoft Entra ID and KeyCloak. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc#rosa-hcp-sts-creating-a-cluster-ext-auth[Creating ROSA with HCP clusters with external authentication].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **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 can customize the domain prefix for the cluster URL by using the `domain-prefix` flag in the ROSA CLI (`rosa`) or by selecting the **Create custom domain prefix** checkbox in the {hybrid-console}. 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].
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Additional Security Groups for {product-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.adoc#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.adoc#rosa-create-machinepool_rosa-managing-objects-cli[create machinepool] section of the ROSA CLI reference.
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **Node management improvements.** Now, you can perform specific tasks to make clusters more efficient. You can cordon, uncordon, and drain a specific node. For more information, see xref:../nodes/nodes/nodes-nodes-working.adoc[Working with nodes].
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Node drain grace periods.** You can now configure node drain grace periods in {hcp-title} clusters with the `rosa` CLI.
|
|
+
|
|
For more information about configuring node drain grace periods, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#rosa-node-drain-grace-period_rosa-managing-worker-nodes[Configuring node drain grace periods in {product-title}].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
[id="rosa-q1-2024_{context}"]
|
|
=== Q1 2024
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Machine pool update.** You can now upgrade machine pools that are configured on ROSA with HCP clusters. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-upgrade-machinepool_rosa-managing-objects-cli[upgrade machinepool].
|
|
|
|
* **{product-title} regions added.** {product-title} is now available in the following regions:
|
|
+
|
|
** Hyderabad (`ap-south-2`)
|
|
** Milan (`eu-south-1`)
|
|
** London (`eu-west-2`)
|
|
** Mumbai (`ap-south-1`)
|
|
** Cape Town (`af-south-1`)
|
|
** Seoul (`ap-northeast-2`)
|
|
** Stockholm (`eu-north-1`)
|
|
+
|
|
For more information on region availabilities, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-hcp-service-definition[Regions and availability zones].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **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.36[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].
|
|
|
|
* **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].
|
|
|
|
* **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.
|
|
|
|
* **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].
|
|
|
|
ifdef::openshift-rosa[]
|
|
[id="rosa-q4-2023_{context}"]
|
|
=== Q4 2023
|
|
|
|
* **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.32[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].
|
|
|
|
* **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].
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* ** {product-title} that uses {hcp} is now generally available.** For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-sts-creating-a-cluster-quickly[Creating {product-title} clusters using the default options].
|
|
endif::openshift-rosa-hcp[]
|
|
* **Configurable process identifier (PID) limits.** With the release of ROSA CLI (`rosa`) version 1.2.31, administrators can use the `rosa create kubeletconfig` and `rosa edit kubeletconfig` commands to set the maximum PIDs for an existing cluster. For more information, see link:https://access.redhat.com/articles/7033551[Changing the maximum number of process IDs per pod (podPidsLimit) for ROSA].
|
|
|
|
* **Configure custom security groups.** With the release of ROSA CLI (`rosa`) version 1.2.31, administrators can use the `rosa create` command or the OpenShift Cluster Manager to create a new cluster or a new machine pool with up to 5 additional custom security groups. Configuring custom security groups gives administrators greater control over resource access in new clusters and machine pools. For more information, see
|
|
ifdef::openshift-rosa[]
|
|
xref:../rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc#rosa-security-groups_prerequisites[Security groups].
|
|
endif::openshift-rosa[]
|
|
ifdef::openshift-rosa-hcp[]
|
|
xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-security-groups_rosa-hcp-prereqs[Security groups].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **Command update.** With the release of ROSA CLI (`rosa`) version 1.2.28, a new command, `rosa describe machinepool`, was added that allows you to check detailed information regarding a specific ROSA cluster machine pool. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-describe-machinepool_rosa-managing-objects-cli[describe machinepool].
|
|
|
|
* **Documentation update.** The Operators section was added to the ROSA documentation. Operators are the preferred method of packaging, deploying, and managing services on the control plane. For more information, see xref:../operators/index.adoc[Operators overview].
|
|
|
|
* **{VirtProductName} support.** The release of {VirtProductName} 4.14 added support for running {VirtProductName} on {product-title} clusters. For more information, see link:https://docs.openshift.com/container-platform/4.14/virt/install/preparing-cluster-for-virt.html#virt-aws-bm_preparing-cluster-for-virt[{VirtProductName} on AWS bare metal] in the {OCP} documentation.
|
|
|
|
[id="rosa-q3-2023_{context}"]
|
|
=== Q3 2023
|
|
|
|
* **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.27[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].
|
|
|
|
* **Cluster autoscaling.** You can now enable cluster autoscaling using ROSA clusters. Cluster autoscaling automatically adjusts the size of a cluster so that all pods have a place to run, and there are no unneeded nodes. You can enable autoscaling during and after cluster creation using either OpenShift Cluster Manager or the ROSA CLI (`rosa`). For more information, see xref:../rosa_cluster_admin/rosa-cluster-autoscaling.adoc#rosa-cluster-autoscaling[Cluster autoscaling].
|
|
|
|
* **Shared virtual private clouds.** {product-title} now supports installing clusters into VPCs shared among AWS accounts that are part of AWS organizations. AWS account installing {rosa-classic-title} clusters can now use shared subnets owned by a management account. For more information, see xref:../rosa_install_access_delete_clusters/rosa-shared-vpc-config.adoc[Configuring a shared virtual private cloud for {product-title} clusters].
|
|
|
|
* **Machine pool disk volume size.** You can now configure your machine pool disk volume size for additional flexibility. You can select your own sizing for the disk volumes of their worker machine pool nodes. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#configuring_machine_pool_disk_volumerosa-managing-worker-nodes[Configuring machine pool disk volume].
|
|
|
|
* **Machine pool update.** You can now add taints to the machine pool that is automatically generated during cluster creation. You can also delete this machine pool. This new feature provides more flexibility and cost-effectiveness for cluster administrators, specifically in regards to scaling infrastructure based on changing resource requirements. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_a_machine_pool_rosa-managing-worker-nodes[Creating a machine pool].
|
|
|
|
* **{product-title} regions added.** {product-title} is now available in the following regions:
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **ROSA regions added.** {product-title} (ROSA) is now available in the following regions:
|
|
+
|
|
** Spain (`eu-south-2`)
|
|
** Hyderabad (`ap-south-2`)
|
|
** Melbourne (`ap-southeast-4`)
|
|
** Zurich (`eu-central-2`)
|
|
+
|
|
For more information on region availabilities, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **Documentation update.** The CLI Tools section was added to the ROSA documentation and includes more detailed information to help you fully use all of the supported CLI tools. The ROSA CLI section can now be found nested inside the CLI Tools heading. For more information, see xref:../cli_reference/index.adoc[CLI tools overview].
|
|
|
|
* **Documentation update.** The Monitoring section in the documentation was expanded and now includes more detailed information to help you conveniently manage your ROSA clusters. For more information, see xref:../observability/monitoring/about-ocp-monitoring/about-ocp-monitoring.adoc#about-ocp-monitoring[About {product-title} monitoring].
|
|
|
|
[id="rosa-q2-2023_{context}"]
|
|
=== Q2 2023
|
|
|
|
* **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.23[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].
|
|
|
|
* **{product-title} region added.** {product-title} is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **ROSA region added.** {product-title} (ROSA) is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
[id="rosa-q1-2023_{context}"]
|
|
=== Q1 2023
|
|
|
|
* **OIDC provider endpoint URL update.** Starting with ROSA CLI version 1.2.7, all new cluster OIDC provider endpoint URLs are no longer regional. Amazon CloudFront is part of this implementation to improve access speed, reduce latency, and improve resiliency. This change is only available for new clusters created with ROSA CLI 1.2.7 or later. There are no supported migration paths for existing OIDC provider configurations.
|
|
endif::openshift-rosa[]
|
|
|
|
[id="rosa-known-issues_{context}"]
|
|
== Known issues
|
|
|
|
// Commenting the first three of these out as part of the Whats new pruning task as these bugs have been resolved. Will need to revisit the Known and Fixed issues sections of this doc and get more in line with what OCP core docs are advising in relation to both.
|
|
//ifdef::openshift-rosa[]
|
|
//* While {egress-zero} works across all supported versions of ROSA, Red Hat suggests you upgrade your cluster or build a cluster to the latest z-stream for your {ocp}. Due to an upstream issue with the internal image registry functionality in disconnected environments, you may experience issues with various {ocp} components within your cluster until you upgrade your version of HCP to the latest z-stream. If you are using older z-stream ROSA clusters with the {egress-zero} feature, you must include a public route to the internet from your cluster. See link:https://issues.redhat.com/browse/OCPBUGS-44314[OCPBUGS-44314] for further details.
|
|
//endif::openshift-rosa[]
|
|
//ifdef::openshift-rosa-hcp[]
|
|
//* While {egress-zero} works across all supported versions of ROSA, Red Hat suggests you upgrade your cluster or build a cluster to the latest z-stream for your {ocp}. Due to an upstream issue with the internal image registry functionality in disconnected environments, you may experience issues with various {ocp} components within your cluster until you upgrade your version of HCP to the latest z-stream. If you are using older z-stream ROSA clusters with the {egress-zero} feature, you must include a public route to the internet from your cluster. See link:https://issues.redhat.com/browse/OCPBUGS-44314[OCPBUGS-44314] for further details.
|
|
//endif::openshift-rosa-hcp[]
|
|
|
|
//* {OCP} 4.14 introduced an updated HAProxy image from 2.2 to 2.6. This update created a change in behavior enforcing strict RFC 7230 compliance, rejecting requests with multiple `Transfer-Encoding` headers. This may cause exposed pods in {product-title} 4.14 clusters sending multiple `Transfer-Encoding` headers to respond with a `502 Bad Gateway` or `400 Bad Request error`. To avoid this issue, ensure that your applications are not sending multiple `Transfer-Encoding` headers. For more information, see link:https://access.redhat.com/solutions/7055002[Red Hat Knowledgebase article]. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*])
|
|
//* If you configure your cluster using external OIDC configuration and set the `--user-auth` flag to `disabled`, the console pods might enter a crash loop. (link:https://issues.redhat.com/browse/OCPBUGS-29510[*OCPBUGS-29510*])
|
|
* The OpenShift Cluster Manager roles (`ocm-role`) and user roles (`user-role`) that are key to the {product-title} provisioning wizard might get enabled accidentally in your Red{nbsp}Hat organization by another user. However, this behavior does not affect the usability.
|
|
* The `htpasswd` identity provider does not function as expected in all scenarios against the `rosa create admin` function.
|
|
|
|
include::modules/rosa-update-cli-tool.adoc[]
|
|
|
|
[id="rosa-deprecated-removed-features_{context}"]
|
|
== Deprecated and removed features
|
|
Some features available in previous releases have been deprecated or removed. Deprecated functionality is still included in {product-title} and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments.
|
|
|
|
ifdef::openshift-rosa-hcp[]
|
|
* **Disable workload monitoring**. Previously, users could disable workload monitoring on {product-title} clusters. However, to allow users to own the full Cluster Monitoring Operator (CMO) stack on {product-title} clusters, the ability to disable workload monitoring has been deprecated. For more information, see xref:../observability/monitoring/configuring-user-workload-monitoring/preparing-to-configure-the-monitoring-stack-uwm.adoc#preparing-to-configure-the-monitoring-stack-uwm[Preparing to configure the user workload monitoring stack].
|
|
endif::openshift-rosa-hcp[]
|
|
|
|
* **ROSA non-STS deployment mode.** ROSA non-STS deployment mode is no longer the preferred method for new clusters. Instead, users must deploy ROSA with the STS mode. This deprecation is in line with our new ROSA provisioning wizard UI experience on the link:https://console.redhat.com/openshift/create/rosa/wizard[Red Hat Hybrid Cloud Console].
|
|
|
|
* **Label removal on core namespaces.** {product-title} is no longer labeling OpenShift core using the `name` label. Customers should migrate to referencing the `kubernetes.io/metadata.name` label if needed for Network Policies or other use cases.
|