Fix file permissions Most likely your kubectl files are not owned by your user. You can set these permissions using below command. sudo chown -R $USER $HOME/.kube Run kubectl with sudo Alternatively you can run kubectl as sudo user using a persistent sudo shell. sudo -s then run your kubectl commands kubectl get pods kubectl … Read more
On the host machine you can use the ssh-key and ip subcommands of the minikube command: scp -i $(minikube ssh-key) <local-path> docker@$(minikube ip):<remote-path> So the command from the question becomes: scp -i $(minikube ssh-key) /media/myuser/sourceFolder docker@$(minikube ip):/home/docker/destiationFolder
Here’s what worked for me: minikube start minikube addons enable ingress minikube addons enable ingress-dns Wait until you see the ingress-nginx-controller-XXXX is up and running using Kubectl get pods -n ingress-nginx Create an ingress using the K8s example yaml file Update the service section to point to the NodePort Service that you already created Append … Read more
You are mostly facing this issue when you use minikube ip which returns 127.0.0.1. It should work if you use internal ip from kubectl get node -o wide instead of 127.0.0.1. A much easier approach from the official reference docs is you can get the url using minikube service web-test –url and use it in … Read more
That happens because of the way netstat renders output. It has nothing to do with actual Kubernetes. I have Docker Desktop for Windows and it adds this to the hosts file: # Added by Docker Desktop 192.168.43.196 host.docker.internal 192.168.43.196 gateway.docker.internal # To allow the same kube context to work on the host and the container: … Read more
stop the minikube: minikube stop clean up the current minikune config and data ( which is not working or gone bad) rm -rf ~/.minikube Start minikube again: ( a fresh instance ) minikube start
You may have some proxy problems. Try following commands: $ unset http_proxy $ unset https_proxy and repeat your kubectl call.
Figured out the issue. VirtualBox was not installed correctly as Mac had blocked it. It wasn’t obvious at first. Restarting won’t work if VirtualBox isn’t installed correctly. System Preferences -> Security & Privacy -> Allow -> Then allow the software corporation (in this case Oracle) Restart Now it worked as expected.
For anyone else here, if using helm to manage your deployments, you need to set initialDelaySeconds it in the deployments.yaml template in the /templates folder under livenessProbe. The livenessProbe will force restart your pod if the probe cannot connect, as was happening with mine. It wasn’t giving my application enough time to build.