[
https://issues.apache.org/jira/browse/FLINK-22802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386350#comment-17386350
]
Yang Wang commented on FLINK-22802:
-----------------------------------
When I bump the fabric8 Kubernetes client version from 4.5.2 to 4.9.2, I got
the information from the author of this repository that they have done lots of
refactoring and changes to support openshift from 4.10 and 5.x. That is where
my concerns come from.
Hope my worries are unnecessary. I will attach the PR before next Monday.
> Bump Fabric8 Kubernetes Client to >= 5.X
> ----------------------------------------
>
> Key: FLINK-22802
> URL: https://issues.apache.org/jira/browse/FLINK-22802
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.0, 1.13.1, 1.12.4
> Environment: Kubernetes 1.19/1.20 provided as part of Openshift
> 4.6/4.7
> Flink 1.13.0 and 1.13.1-rc1
> Reporter: Enrique Lacal
> Assignee: Yang Wang
> Priority: Minor
> Labels: auto-deprioritized-major
> Fix For: 1.14.0
>
>
> Hi All,
> Currently, Flink is using version 4.9.2 of the Fabric8 Kubernetes Client
> which does not support new versions of the Kubernetes API such as 1.19 or
> 1.20 as pointed out by their [Compatibility
> Matrix|https://github.com/fabric8io/kubernetes-client#compatibility-matrix]
> which is support in 5.4.0 or above.
> As far as I have seen in the Flink documentation, Flink supports `Kubernetes
> >= 1.9.` but due to this dependency, it might not be the case. Is there a
> plan to update this dependency?
> What is the plan moving forwards when new versions of Kubernetes are released?
> I am raising this because I have been testing Flink HA Session Cluster on
> Kubernetes 1.19 and 1.20 and I have encountered some frequent errors that
> force the JM pods to restart or even result in an unrecoverable state.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
