I would like to simplify the answer a bit further for those who are reletively new to Kubernetes and its ingress options in particular. There are 2 separate things that need to be present for ingress to work: Ingress Controller(essentially a separate Pod/Deployment along with a Service that can be used to utilize routing and … Read more
I am not exactly sure what you are asking as it seems you already know about the minikube service <SERVICE_NAME> –url command which will give you a url where you can access the service. In order to open the exposed service, the minikube service <SERVICE_NAME> command can be used: $ kubectl run hello-minikube –image=gcr.io/google_containers/echoserver:1.4 –port=8080 … Read more
This can be solved by various ways, I suggest better go for kubectl describe pod podname name, you now might see the cause of why the service that you’ve been trying is failing. In my case, I’ve found that some of my key-values were missing from the configmap while doing the deployment.
The stable repository is hosted on https://kubernetes-charts.storage.googleapis.com/. So, try the following: helm repo add stable https://kubernetes-charts.storage.googleapis.com/ EDIT 2020-11-16: the above repository seems to have been deprecated. The following should now work instead: helm repo add stable https://charts.helm.sh/stable
The double dash symbol “–” is used to separate the command you want to run inside the container from the kubectl arguments. So the correct way is: kubectl exec -it –namespace=tools mongo-pod — bash -c “mongo” You forgot a space between “–” and “bash”. To execute multiple commands you may want: to create a script … Read more
kubectl get nodes -o json | jq ‘.items[].spec’ which will give the complete spec with node name, or: kubectl get nodes -o json | jq ‘.items[].spec.taints’ will produce the list of the taints per each node
I’m the author of both of these features. The idea is that you should: Use Secrets for things which are actually secret like API keys, credentials, etc Use ConfigMaps for not-secret configuration data In the future, there will likely be some differentiators for secrets like rotation or support for backing the secret API w/ HSMs, … Read more
Before kubernetes 1.15 the answer is no. But there is a workaround of patching deployment spec with a dummy annotation: kubectl patch deployment web -p \ “{\”spec\”:{\”template\”:{\”metadata\”:{\”annotations\”:{\”date\”:\”`date +’%s’`\”}}}}}” As of kubernetes 1.15 you can use: kubectl rollout restart deployment your_deployment_name CLI Improvements Created a new kubectl rollout restart command that does a rolling restart of … Read more
This works if you have a namespace selected in your context: kubectl config view –minify -o jsonpath=”{..namespace}” Also, kube-ps1 can be used to display your current context and namespace in your shell prompt.