You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Abhayjit Kharbanda (Jira)" <ji...@apache.org> on 2021/05/11 12:12:00 UTC

[jira] [Comment Edited] (KARAF-7149) Karaf cellar still uses 4.6.3 of kubernetes client which isnt compatible with latest k8s versions

    [ https://issues.apache.org/jira/browse/KARAF-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342511#comment-17342511 ] 

Abhayjit Kharbanda edited comment on KARAF-7149 at 5/11/21, 12:11 PM:
----------------------------------------------------------------------

Could you please elaborate on that ? I am using cellar for running a distributed cluster and right now the list pods call fails during discovery . However , if I curl from the pod using the same service account token it is successful . Any workarounds ? 
I am using cluster-group:feature-install and feature-add from cellar


was (Author: abhayjit):
Could you please elaborate on that ? I am using cellar for running a distributed cluster and right now the list pods call fails during discovery . However , if I curl from the pod using the same service account token it is successful . Any workarounds ?

> Karaf cellar still uses 4.6.3 of kubernetes client which isnt compatible with latest  k8s versions
> --------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-7149
>                 URL: https://issues.apache.org/jira/browse/KARAF-7149
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf
>    Affects Versions: 4.3.1
>            Reporter: Abhayjit Kharbanda
>            Assignee: Jean-Baptiste Onofré
>            Priority: Blocker
>
> According to this compatibility matrix of kubernetes-client version 4.6.3 ( which is the one being used in cellar) is compatible only till version 1.15 of k8s which is pretty old . Can we update the version of kubernetes-client ?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)