Cannot start native K8s
Locked
 
|
Hi,
I'm using Flink-1.10 and tested everything [1] successfully. While trying [2], I got the following message. Can anyone help please? [root@DAC-E04-W06 bin]# ./kubernetes-session.sh Thanks, Dongwon |
|
|
Hi Dongwon Kim, I think it is a known issue. The native kubernetes integration could not work with jdk 8u252 due to okhttp issue[1]. Currently, you could upgrade your jdk to a new version to work around. Dongwon Kim <[hidden email]> 于2020年5月6日周三 上午7:15写道：
|
|
|
Hi Dongwon Kim, Are you running Flink on a minikube or a real Kubernetes cluster? I just could not reproduce it in a real Kubernetes cluster with java 8u252. For minikube, i get the exception with you. Best, Yang Yang Wang <[hidden email]> 于2020年5月6日周三 上午9:29写道：
|
|
|
Hello Yang, I'm using K8s v1.18.2 installed by Kubeadm over a cluster of 5 nodes (not a Minikube). Previously, as you pointed out, openjdk version "1.8.0_252" was installed. I bump up java version to openjdk 11.0.7 but got something different:
Thanks a lot for your interest :-) Best, Dongwon On Sat, May 9, 2020 at 11:15 AM Yang Wang <[hidden email]> wrote:
|
|
|
Hi Dongwon Kim, Thanks a lot for your information. I will dig into this issue. I think the "UnknownHostException" is caused by incorrectly setting the Kubernetes ApiServer address. Maybe you are using "kubernetes.default.svc". However, it could not be accessed outside of the Kubernetes cluster. You need to configure a correct ip/hostname for ApiServer address, which could be accessed in your local environment. You could use `kubectl auth can-i create pods` to verify whether the kube config is correct. BTW, currently we only find the flink on native K8s could not work on 8u252. For 8u242 and lower version, it works well. Best, Yang Dongwon Kim <[hidden email]> 于2020年5月9日周六 上午10:43写道：
|
|
|
Hi Yang, Oops, I forget to copy /etc/kube/admin.conf to $HOME/.kube/config so that the current user account can access to K8s. Now that I copied it, I found that kubernetes-session.sh is working fine. Thanks very much! Best, Dongwon
On Sat, May 9, 2020 at 12:29 PM Yang Wang <[hidden email]> wrote:
|
|
|
Glad to hear that you could deploy the Flink cluster on K8s natively. Thanks for trying the in-preview feature and give your feedback. Moreover, i want to give a very simple conclusion here. Currently, because of the compatibility issue of fabric8 kubernetes-client, the native K8s integration have the following known limitation. * For jdk 8u252, the native k8s integration could only work on kubernetes v1.16 and lower versions. * For other jdk versions(e.g. 8u242, jdk11), i am not aware of the same issues. The native K8s integration works well. Best, Yang Dongwon Kim <[hidden email]> 于2020年5月9日周六 上午11:46写道：
|
|
|
A quick update on this issue. The root cause of this issue is compatibility of kubernetes-client and java 8u252[1]. And we have bumped he fabric8 kubernetes-client version from 4.5.2 to 4.9.2 in master and release-1.11 branch. Now users could deploy Flink on K8s natively with java 8u252. If you really could not use the latest Flink version, you could set the environment "HTTP2_DISABLE=true" in Flink client, jobmanager, taskmanager side. Best, Yang Yang Wang <[hidden email]> 于2020年5月11日周一 上午11:51写道：
|
«
Return to (DEPRECATED) Apache Flink User Mailing List archive.
|
1 view|%1 views
| Free forum by Nabble | Edit this page |