[
https://issues.apache.org/jira/browse/FLINK-22802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22802:
-----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Bump Fabric8 Kubernetes Client to >= 5.2.0
> ------------------------------------------
>
> 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
> Priority: Major
> Labels: stale-major
>
> 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 [Compatability Matrix|#compatibility-matrix].]
> which is support in 5.2.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)
