August
v4.2 Update 9 - SaaS¶
17 Aug, 2026
This release includes the following bug fixes that improve platform stability and reliability.
Bug Fixes¶
The following bug fixes are included in this release:
| Bug ID | Description |
|---|---|
| RC-53073 | Fixed an issue where network policy settings were not retained when creating a new blueprint version |
| RC-52931, RC-52882 | Updated Fluent Bit and Helm Exporter to newer platform-supported versions to address known security vulnerabilities |
v4.2 Update 8 - SaaS¶
13 Aug, 2026
This release includes the following bug fixes that improve platform stability and reliability.
Bug Fixes¶
The following bug fixes are included in this release:
| Bug ID | Description |
|---|---|
| RC-52738 | AKS: Fixed an issue where Day 2 operations were incorrectly blocked by validation of the system-generated location field in node pool configurations |
| RC-51436 | GKE: Fixed an issue where GKE node pool upgrades could remain stuck in the Upgrade Queued state due to a race condition between saving the cluster upgrade status and updating node pool conditions. |
| RC-52588 | MKS: Fixed an issue where cluster configuration was incorrectly updated with nameserver changes even when the corresponding nameserver update job failed. |
v4.2 Update 7 - SaaS¶
06 Aug, 2026
This release includes the following enhancement and bug fixes that improve platform stability and reliability.
Azure AKS¶
Cross-Subscription Provisioning¶
You can now provision AKS clusters across multiple Azure subscriptions using a single Service Principal cloud credential. Grant the Service Principal RBAC access (for example, Contributor) in each target subscription, then set clusterConfig.spec.subscriptionID in the cluster spec to deploy to a subscription other than the credential default.
Note
Supported through Terraform, CLI (RCTL), and Save & Customize in the UI.
Benefit
Deploy dev, staging, and production AKS clusters to separate subscriptions from one central credential while keeping identity management unified.
For more information, see Cross-Subscription Provisioning.
v4.2 Update 6 - SaaS¶
03 Aug, 2026
This release includes the following enhancements and bug fixes that improve platform stability and reliability.
EKS Clusters with Only Fargate¶
You can now provision Amazon EKS clusters without managed node groups and configure Fargate profiles to run required blueprint components and operators. This lets you use AWS Fargate or Karpenter-managed node groups for compute without maintaining a dedicated managed node group for Rafay components, reducing infrastructure cost and operational overhead in a Karpenter-managed EKS architecture.
For more information, see EKS Clusters Without Node Groups.
Rafay MKS: Nameserver Overrides¶
Rafay MKS clusters now support optional Nameserver Overrides during day-0 provisioning and as a day-2 operation. This setting is useful in environments that use private DNS servers to resolve cluster domains and need to specify upstream nameservers for cluster DNS forwarding.
Configure nameserver overrides through the UI, API, Terraform, or CLI (RCTL).
For configuration details and examples, see Nameserver Overrides.
Bug Fixes¶
The following bug fixes are included in this release:
| Bug ID | Description |
|---|---|
| RC-51796 | Duplicate entry seen for the cluster object |
| RC-51909 | Retry option not shown when a failed Kubernetes upgrade is viewed on the cluster activity page |
| RC-51394 | EKS: All Day2 operations Failing with no rows in result set. Cluster config is not found. |
| RC-50083 | Fleet UI: Default project labels are not populating in the default project |
| RC-52121 | EKS: Nodegroup label update taskset stuck in "INPROGRESS" on EKS clusters , however labels get updated on the cluster |