You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "wangqi (Jira)" <ji...@apache.org> on 2022/07/06 00:43:00 UTC

[jira] [Updated] (FLINK-28412) kubernetes-client doesn't infer kubeconfig encryption algorithm and fails on k3s

     [ https://issues.apache.org/jira/browse/FLINK-28412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

wangqi updated FLINK-28412:
---------------------------
    Summary: kubernetes-client  doesn't infer kubeconfig encryption algorithm and fails on k3s  (was: kubernetes-client  doesn't infer kubeconfig encryption algorithm and failed on k3s)

> kubernetes-client  doesn't infer kubeconfig encryption algorithm and fails on k3s
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-28412
>                 URL: https://issues.apache.org/jira/browse/FLINK-28412
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.14.2, 1.13.6, 1.14.3, 1.14.4, 1.15.0
>            Reporter: wangqi
>            Priority: Major
>
> [k3s|https://github.com/k3s-io/k3s] is a lightweight and has fully conformant production-ready Kubernetes distribution.
> k3s kube config use a different encryption algorithm which not same with Kubernetes config, and kubernetes-client also doesn't infer kube config encryption algorithm until 5.10.0 version.
> kubernetes-client fixes k3s kube config compatibility through [issue|https://github.com/fabric8io/kubernetes-client/issues/3535] and works from 5.10.0 version.
> flink-kubernetes module now uses 5.5.0 version and submitting to k3s would fail



--
This message was sent by Atlassian Jira
(v8.20.10#820010)