[flink-kubernetes-operator] branch release-1.2 updated: [docs][hotfix] Remove standolane support from known limitations

[mb...@apache.org]

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

mbalassi pushed a commit to branch release-1.2
in repository https://gitbox.apache.org/repos/asf/flink-kubernetes-operator.git


The following commit(s) were added to refs/heads/release-1.2 by this push:
     new 1ec61016 [docs][hotfix] Remove standolane support from known limitations
1ec61016 is described below

commit 1ec6101601108e9de2f490704f9c3befb0627595
Author: Marton Balassi <ma...@apple.com>
AuthorDate: Thu Dec 8 12:12:07 2022 +0100

    [docs][hotfix] Remove standolane support from known limitations
---
 docs/content/docs/concepts/overview.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/content/docs/concepts/overview.md b/docs/content/docs/concepts/overview.md
index d1aeb6b9..e5324e74 100644
--- a/docs/content/docs/concepts/overview.md
+++ b/docs/content/docs/concepts/overview.md
@@ -90,9 +90,6 @@ The examples are maintained as part of the operator repo and can be found [here]
 ### JobManager High-availability
 The Operator leverages [Kubernetes HA Services](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/) for providing High-availability for Flink jobs. The HA solution can benefit form using additional [Standby replicas](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/overview/), it will result in a faster recovery time, but Flink jobs will still restart when the Leader JobManager goes down.
 
-### Standalone Kubernetes Support
-The Operator does not support [Standalone Kubernetes](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/standalone/kubernetes/) deployments yet. It is expected to be part of the `1.2.0` release.
-
 ### JobResultStore Resource Leak
 To mitigate the impact of [FLINK-27569](https://issues.apache.org/jira/browse/FLINK-27569) the operator introduced a workaround [FLINK-27573](https://issues.apache.org/jira/browse/FLINK-27573) by setting `job-result-store.delete-on-commit=false` and a unique value for `job-result-store.storage-path` for every cluster launch. The storage path for older runs must be cleaned up manually, keeping the latest directory always:
 ```shell