diff --git a/src/docs/ocean/features/auto-update-process-gke.md b/src/docs/ocean/features/auto-update-process-gke.md index faa38bcc9..dc3862eb3 100644 --- a/src/docs/ocean/features/auto-update-process-gke.md +++ b/src/docs/ocean/features/auto-update-process-gke.md @@ -28,7 +28,18 @@ As an example, let’s say you have created an Ocean cluster with VNGs using the 3. The Ocean-managed VNGs are updated with the new labels to reflect the added NodeLocal DNSCache. 4. The changes become effective in Ocean, and the daemonset is scheduled as expected. -## Manually trigger the Auto-Update Process +## Turn the Auto-Update Process on or off for Your Clusters + +You can decide whether to run the auto-update process via the Spot API at the cluster level (under cluster). + +* [Create Cluster](https://docs.spot.io/api/#tag/Ocean-GKE/operation/OceanGKEClusterCreate) +* [Update Cluster](https://docs.spot.io/api/#tag/Ocean-GKE/operation/OceanGKEClusterUpdate) + +By default, `autoUpdate = true` + +Set `autoUpdate = false` to turn off auto-update. + +## Manually Trigger the Auto-Update Process The auto-update process described above occurs every 30 minutes (by default). If you do not want to wait, use the [Reimport Cluster](https://docs.spot.io/api/#operation/reImportGke) in the Spot API to trigger the auto-update process manually. @@ -40,3 +51,8 @@ Example: You will immediately see your changes in the relevant Ocean cluster or Virtual Node Group configurations. + + + + + diff --git a/src/docs/ocean/release-notes/README.md b/src/docs/ocean/release-notes/README.md index a0b74fd6c..401e97c33 100644 --- a/src/docs/ocean/release-notes/README.md +++ b/src/docs/ocean/release-notes/README.md @@ -3,6 +3,12 @@ ## December 2024: Features and Enhancements +* **OCN-0053: December 17, 2024:** (**GKE**) You can now run the GKE Auto-Update process for your clusters via the Spot API `autoUpdate` attribute. [Learn more...](https://docs.spot.io/ocean/features/auto-update-process-gke) + +* **OCN-0052: December 17, 2024:** (**GKE**) Our new `revertToPreferred` attribute ensures that Ocean always runs your workloads on your most preferred instance types. You can configure `revertToPreferred` at cluster and virtual node group levels. [Learn more...](https://docs.spot.io/ocean/features/vngs/attributes-and-actions-per-vng?id=revert-to-preferred-instance-types-per-virtual-node-group-gke) + +* **OCN-0051: December 17, 2024:** (**GKE**) As part of the 1.30 version, Kubernetes has released [Support for Pod Scheduling Readiness](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-scheduling-readiness/), which allows stating if a pod is ready to be scheduled or not. GKE now supports this feature for any cluster using the new Ocean Controller v2 and Kubernetes version 1.30 and above. + * **OCN-0050: December 10, 2024:** (**AKS**) Ocean now supports setting virtual node group shutdown hours via the Spot API. [Learn more...](https://docs.spot.io/ocean/tutorials/set-running-hours?id=schedule-shutdown-hours-in-the-api-per-virtual-node-group) * **OCN-0049: December 10, 2024:** (**AKS**) Check out the new Auto-Upgrades feature in the Ocean AKS clusters console. Use this feature to automate your clusters' control plane patch version updates, saving time and reducing manual effort and potential errors. [Learn more...](https://docs.spot.io/ocean/features/auto-upgrade-aks-patch-version) @@ -15,6 +21,7 @@ Previous months... +
November, 2024 - click to view