(flink-web) 01/02: Add standalone autoscaler notes to operator release

[mx...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mxm pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git

commit 60bbfbd0bf8fd074266ba4579087b589a7b1698c
Author: Maximilian Michels <mx...@apache.org>
AuthorDate: Mon Mar 25 12:30:35 2024 +0100

    Add standalone autoscaler notes to operator release
---
 .../posts/2024-03-21-release-kubernetes-operator-1.8.0.md      | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/content/posts/2024-03-21-release-kubernetes-operator-1.8.0.md b/docs/content/posts/2024-03-21-release-kubernetes-operator-1.8.0.md
index 559e432a1..c955ee912 100644
--- a/docs/content/posts/2024-03-21-release-kubernetes-operator-1.8.0.md
+++ b/docs/content/posts/2024-03-21-release-kubernetes-operator-1.8.0.md
@@ -99,6 +99,16 @@ For the next release we are thinking to enable it by default.
 
 Autoscaling used to be an application / job cluster only feature. Now it is also supported for session clusters.
 
+### Improved Standalone Autoscaler
+
+Since 1.7.0, Flink Autoscaling is now also available in a standalone module without the need to run on top of Kubernetes.
+
+We merged notable improvements to the standalone autoscaler:
+
+- The control loop now supports multiple thread
+- We implemented a JdbcAutoScalerStateStore for storing state via JDBC-supported databases
+- We implemented a JdbcAutoScalerEventHandler for emitting events to JDBC-supported databases
+
 ### Savepoint Trigger Nonce
 
 A common request is to support a streamlined, user-friendly way of redeploying from a target savepoint. Previously this