I am new to play with k8s(https://labs.play-with-k8s.com). I am able to install helm on Master node. I have added helm repo bitnami. But, I am getting below error while trying to install bitnami/kafka using command below
helm install my-kafka bitnami/kafka
Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "https://192.168.0.8:6443/version": dial tcp 192.168.0.8:6443: connect: connection refused
Can someone help me on steps to resolve this issue please?
Related
I have just installed Rancher for test purpose. First I install docker and I install kubectl and helm. Then I install Rancher. When I try to create a new kubernetes cluster, I got this error. I searched about it and it is about the certification error I thought.
Failed to create fleet-default/aefis-test cluster.x-k8s.io/v1beta1, Kind=Cluster for rke-cluster fleet-default/aefis-test: Internal error occurred: failed calling webhook "default.cluster.cluster.x-k8s.io": failed to call webhook: Post "https://webhook-service.cattle-system.svc:443/mutate-cluster-x-k8s-io-v1beta1-cluster?timeout=10s": service "webhook-service" not found"
I used this command to install Rancher:
sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher:latest --no-cacerts"
I hope anybody has a good idea and solution for this error? Thanks.
If I want to delete the webhood secret for triggering to create new one, it throws this error:
The connection to the server localhost:8080 was refused - did you specify the right host or port?
I am trying to install Orion. I used "helm install my-orion-ld openshift/orion-ld --version 1.0.3" but I get this error :
Error: INSTALLATION FAILED: failed to download "openshift/orion-ld" at version "1.0.3"
Also when I am trying to install it through local tgz file that has been provided I get the this error :
Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version": dial tcp 127.0.0.1:8080: connect: connection refused
I searched for the solution and with the help of this post I created config file in the .kobe folder in home directory but I still couldn't manage to install this chart.
I guess there is something wrong with my Helm chart installation. But when I run "helm version" command I see the correct output that seems helm is working correctly :
"version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.17.5"}"
I am attempting to run compose up and am running the following command sudo kompose up --push-image=false --verbose kompose builds all the containers successfully but right at the very end throws this error:
FATA Error while deploying application: Get https://127.0.0.1:6443/api: dial tcp 127.0.0.1:6443: connect: connection refused
I have even run kubectl proxy but this didn't fix the problem, can anyone please help?
EDIT: To clarify I am using minikube, it is running in the background but Kompose still doesn't work.
Turns out the issue ended up being the fact that the certificates for the kubectl proxy commanded were not self signed by default, I got around this using kompose up --server http://127.0.0.1:6443 but I cannot use the Kubernetes Dashboard without the certificates.
I have just installed Kubernetes on my MacOS using homebrew.
Now, in the terminal, I ran kubectl version command and the error message reads Unable to connect to the server: dial tcp 35.225.115.157:443: i/o timeout
How to solve this issue?
kubectl version makes a connection to both client and server (kubernetes master) in order to print the versions.
Run kubectl cluster-info and check if the server is up.
I am following the CoreOS tutorial for self-hosted Kubernetes and I am having some issues with the Bootkube API server. Using the Bootkube example from the recommended repository I have only changed the ssh_authorized_keys metadata field in nodes 1,2 and 3. All other settings are the same as in the repository. However, after running bootkube-start via systemctl on node1 I check the logs using ssh core#node1.example.com 'journalctl -f -u bootkube' and I am getting Unable to determine api-server readiness: Get https://node1.example.com:443/version: dial tcp 172.17.0.21:443: getsockopt: connection refused. Does anyone know of the best ways to debug such an issue?
It looks like the api-server is having issues while starting, or that you have some networking/firewall/dns problem.
You should be able to ssh core#node1.example.com and then get the full bootkube logs there via sudo journalctl -u bootkube.