If you add multiple certificates in tls.cert key in Kubernetes TLS Ingress Configuration. Please do this like this —–BEGIN CERTIFICATE—– <put your certificate value in a single line > —–END CERTIFICATE—– —–BEGIN INTERMEDIATE CERTIFICATE—– <put your certificate value in a single line> —–END INTERMEDIATE CERTIFICATE—– Otherwise, you’ll get an error in ssl cert chain validation. … Read more
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
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
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
In my case the problem was that somehow context was changed. Checked it by kubectl config current-context and then changed it back to the correct one by kubectl config use-context docker-desktop