v3.7 Update 2 - SaaS¶
04 Nov, 2025
Upstream Kubernetes for Bare Metal and VMs¶
Automated Binary Cleanup on Cluster and Node Deletion¶
Benefit
Ensures complete cleanup of binaries and libraries installed during cluster provisioning, preventing leftover artifacts and reducing manual cleanup efforts.
When deleting a cluster or node, the platform now automatically runs conjurer -d to remove all binaries and libraries that were installed during cluster bring-up or conjurer execution. This enhancement ensures:
-
Cluster Deletion: During cluster deletion,
conjurer -dis executed at the end of the process to remove all binaries installed on the nodes as part of cluster provisioning or conjurer runs. -
Node Deletion: When deleting a node that is up and running, the platform removes the node from the platform and automatically runs
conjurer -don the node to remove all installed libraries that were added during cluster bring up.
This automated cleanup process helps maintain clean infrastructure and prevents accumulation of leftover binaries and libraries on nodes.
Bug Fix¶
| Bug ID | Description |
|---|---|
| RC-44915 | Upstream K8s: Fixed an issue where Day 2 master node addition failed post an upgrade from Kubernetes 1.32 to 1.33. |
| RC-44692 | Upstream K8s: Fixed an issue where node addition failed when nodes were in different subnets while using Calico CNI. |