1996fanrui commented on code in PR #699: URL: https://github.com/apache/flink-web/pull/699#discussion_r1399020266
########## docs/content/posts/2023-11-23-release-kubernetes-operator-1.7.0.md: ########## @@ -17,32 +20,41 @@ We encourage you to [download the release](https://flink.apache.org/downloads.ht Previously the operator only added more and more supported Flink versions without a policy to remove support for these in the future. This resulted in a lot of legacy codepaths already in the core logic. -To keep things clean and easy to move forward at a reasonable pace, the community decided to adopt a new version support policy. +To keep technical debt at reasonable levels, the community decided to adopt a new Flink version support policy for the operator. {{< hint danger >}} Starting from 1.7.0 the operator will only support the last 4 Flink minor versions corresponding to the date of the operator release. For 1.7.0 this translates to: 1.18, 1.17, 1.16, 1.15 {{< /hint >}} -The operator will simply ignore changes made to resources with unsupported Flink versions. This also means that resources with unsupported versions are not possible to delete once the operator is upgraded. To temporarily work around this, users can upgrade the Flink version of the resource before trying to delete it. +The operator will simply ignore changes made to resources with unsupported Flink versions. This also means that resources with unsupported versions are not possible to delete once the operator is upgraded. To temporarily work around this, users can upgrade the Flink version of the resource before deleting it. ## Highlights ### Decoupled Autoscaler Module -Starting from 1.7.0, Autoscaler is decoupled from kubernetes-operator. `flink-autoscaler` is an -independent module of `flink-kubernetes-operator`, but it does not contain any `kubernetes-related` -dependencies. `flink-autoscaler` defines a series of generic interfaces, read -[Extensibility of Autoscaler](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.7/docs/custom-resource/autoscaler/#extensibility-of-autoscaler) -get more information. +Starting from 1.7.0, the autoscaler logic is decoupled from Kubernetes and the Flink Kubernetes Operator. +The `flink-autoscaler` module now does not contain any Kubernetes related dependencies but defines a set of generic interfaces that are implemented by the operator. -In addition, the first version of `Autoscaler Standalone` is already supported. It supports single -Flink cluster, it can be any type of Flink cluster, includes: `Flink Standalone Cluster`, `MiniCluster`, -`Flink yarn session cluster`, `Flink yarn application cluster`, etc. `Autoscaler Standalone` runs as a -separate Java Process and is very simple, read [Autoscaler Standalone](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.7/docs/custom-resource/autoscaler/#autoscaler-standalone) -to see how to run it. +As part of the decoupling effort, we released the initial version of the `Standalone Autoscaler` which serves as a limited alternative for anyone not using the Flink Kubernetes Operator currently. It supports scaling a single Flink cluster that can be any type, including: `Flink Standalone Cluster`, `MiniCluster`, `Flink YARN session cluster`, `Flink YARN application cluster`. -Read more about this in the original [FLIP](https://cwiki.apache.org/confluence/display/FLINK/FLIP-334+%3A+Decoupling+autoscaler+and+kubernetes+and+support+the+Standalone+Autoscaler) +The Standalone Autoscaler runs as a separate Java Process. Please read the [Autoscaler Standalone](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.7/docs/custom-resource/autoscaler/#autoscaler-standalone) section for setup instructions. The standalone autoscaler is limited to Flink version 1.18. + +To benefit from the best possible integration we recommend using the autoscaler as part of the Flink Kubernetes Operator. The standalone autoscaler is not planned to replace this either now or in the future. + +To align with the new structure the autoscaler related configs will lose the `kubernetes.operator.` prefix going forward: Review Comment: Good catch! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
