The standalone mode will be supported in the release-1.2, which is
expected to be released at the beginning of October.
Best,
Yang
Javier Vegas 于2022年9月12日周一 04:52写道：
> Hi, Yang!
>
> When you say the operator uses native k8s integration by default, does
> that mean there is a way to change that
Hi, Yang!
When you say the operator uses native k8s integration by default, does that
mean there is a way to change that to use standalone K8s? I haven't seen
anything about that in the docs, besides a mention that standalone support
is coming in version 1.2 of the operator.
Thanks,
Javier
On
Since the flink-kubernetes-operator is using native K8s integration[1] by
default, you need to give the permissions of pod and deployment as well as
ConfigMap.
You could find more information about the RBAC here[2].
[1].
https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/deployment/r
I am migrating a HA standalone Kubernetes app to use the Flink operator.
The HA store is S3 using IRSA so the app needs to run with a serviceAccount
that is authorized to access S3. In standalone mode HA worked once I gave
the account permissions to edit configMaps. But when trying the operator
wit
