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
Kind cluster configuration needs to be like below apiVersion: kind.x-k8s.io/v1alpha4 kind: Cluster nodes: – role: control-plane extraPortMappings: – containerPort: 30000 hostPort: 30000 listenAddress: “0.0.0.0” # Optional, defaults to “0.0.0.0” protocol: tcp # Optional, defaults to tcp – role: worker This file is then passed to your creation command as kind create cluster –config=config.yaml (according to … Read more
This package contains in deb http://ftp.de.debian.org/debian buster main repo which is not available in ubuntu. First you need to do add this to /etc/apt/sources.list like below #for kubectlx deb [trusted=yes] http://ftp.de.debian.org/debian buster main Then run sudo apt-get update Then you can install using this cmd. sudo apt install kubectx
If you change the selector label, then you will need to purge the release first before deploying: kubectl delete deploy <deployment-name>
The short answer, is you cannot. Why? Because busybox does not have package manager like: yum, apk, or apt-get .. Acutally you have two solutions: 1. Either use a modified busybox You can use other busybox images like progrium/busybox which provides opkg-install as a package manager. image: progrium/busybox Then: kubectl exec -it busybox — opkg-install … 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
By default, helm3 only shows releases of default namespace. Do the following to get your release and delete it. # Get all releases helm ls –all-namespaces # OR helm ls -A # Delete release helm uninstall release_name -n release_namespace
Kubernetes can’t make that substitution for you, you should do it with shell in the entrypoint of the container. This is a working example. I modify the default entrypoint to create a new variable with that substitution. After this command you should add the desired entrypoint. apiVersion: extensions/v1beta1 kind: Deployment metadata: name: app labels: app: … Read more
A pod is running as long as one of the containers is running. If you need them to exit together, you have to arrange that the sidecar dies. We do not have a notion of “primary” vs “secondary” containers wrt lifecycle, though that’s sort of interesting. One option would be to use an emptyDir volume … Read more