[ https://issues.apache.org/jira/browse/FLINK-32408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735717#comment-17735717 ]
dongwoo.kim edited comment on FLINK-32408 at 6/21/23 1:21 PM: -------------------------------------------------------------- I think this is fixed in new version because in main branch's pom.xml, flink version is updated from *1.16.1* to *1.17.1.* But then I'm curious whether we can say that kubernetes-operator-1.5.0 supports flink 1.17 version, since they had flink version to 1.16.1 was (Author: JIRAUSER300481): I think this is fixed in new version because in main branch's pom.xml, flink version is updated from *1.16.1* to *1.17.1.* But then I'm curious whether we can say that kubernetes-operator-1.5.0 supports flink 1.17 version. > JobManager HA configuration update needed in Flink k8s Operator > ---------------------------------------------------------------- > > Key: FLINK-32408 > URL: https://issues.apache.org/jira/browse/FLINK-32408 > Project: Flink > Issue Type: Bug > Components: Kubernetes Operator > Affects Versions: kubernetes-operator-1.5.0 > Reporter: dongwoo.kim > Priority: Minor > Fix For: kubernetes-operator-1.6.0 > > > In flink 1.17 documentation it says, to configure job manger ha we have to > configure *high-availability.type* key not *high-availability* key{*}.{*} (It > seems to be changed from 1.17) > And currently kubernetes-operator-1.5.0 says it supports flink 1.17 version. > So I expected that configuring job manager ha with *high-availability.type* > should work but it didn't, only *high-availability* works > *ref* > [https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/deployment/config/#high-availability] > > [https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.5/docs/concepts/overview/#core] > -- This message was sent by Atlassian Jira (v8.20.10#820010)