search

GoogleCloudPlatform / flink-on-k8s-operator

[DEPRECATED] Kubernetes operator for managing the lifecycle of Apache Flink and Beam applications.
Apache License 2.0
659 stars 265 forks source link

Internal error occurred: failed calling webhook "mflinkcluster.flinkoperator.k8s.io" #400

Open ilyak77 opened 3 years ago

ilyak77 commented 3 years ago

Beginner question:

our study group try to learn and run the demo. When we ran the make deploy, it failed in pull image. So we try to run each yaml file seperately.

kubectl apply -f flinkoperator_v1beta1_remotejobjar.yaml, it returns error like:

"flinkoperator_v1beta1_remotejobjar.yaml": Internal error occurred: failed calling webhook "mflinkcluster.flinkoperator.k8s.io": Post "https://flink-operator-webhook-service.flink-operator-system.svc:443/mutate-flinkoperator-k8s-io-v1beta1-flinkcluster?timeout=30s": dial tcp 10.190.33.155:443: connect: connection refused

Our OS is centos 8.1 and kubectl version is Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-18T12:09:25Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-18T12:00:47Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

Is that due to our k8s node configuration issue or a network issue? if the later one, is there any place we could get those images directory? thanks!

banbushi commented 2 years ago

I restart the docker and kubelet and resolved the problem，but not a real way。。