It would appear that you are attempting to deploy Kubernetes leveraging kubeadm but have skipped the step of Installing a pod network add-on (CNI). Notice the warning: The network must be deployed before any applications. Also, CoreDNS will not start up before a network is installed. kubeadm only supports Container Network Interface (CNI) based networks … Read more
/usr/bin/env exports values passed in key=value pairs into the environment of any program it’s used to invoke. kubectl -n nmspc exec “$POD” — env curIP=123 script01 Note that you should never use $runScript or any other unquoted expansion to invoke a shell command. See BashFAQ #50 — I’m trying to put a command in a … Read more
In addition to Jonas’ answer above; If you have more than one namespace, you need to specify the namespace your pod is currently using i.e kubectl exec -n <name space here> <pod-name> -it — /bin/sh After successfully accessing your pod, you can go ahead and navigate through your container.
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
This is a reasonably common, but not universal, Un*x convention. (It is mentioned in the POSIX specification and so most non-Linux Unices will support it as well.) The important detail here is that the kubectl … -f option expects a filename. If you have a file named x.yaml, a more direct way to write what … Read more
For newer versions of kubectl, adding a retries=-1 flag may resolve the issue: kubectl cp –retries=-1 pod-www-xxx-yyy-zzz:/path/to/remote/dir ~/local/dir
Something like this will do the trick (you must have jq installed): $ kubectl get pod –namespace=xx yyyy -o json | jq ‘.status.containerStatuses[] | { “image”: .image, “imageID”: .imageID }’ { “image”: “nginx:latest”, “imageID”: “docker://sha256:b8efb18f159bd948486f18bd8940b56fd2298b438229f5bd2bcf4cedcf037448” } { “image”: “eu.gcr.io/zzzzzzz/php-fpm-5:latest”, “imageID”: “docker://sha256:6ba3fe274b6110d7310f164eaaaaaaaaaa707a69df7324a1a0817fe3b475566a” }
I believe the “kubectl way” is to not background the proxy at all as it is intended to be a short running process to access the API on your local machine without further authentication. There is no way to stop it other than kill or ^C (if not in background). You can use standard shell … Read more
You can do this through the raw command. kubectl get –raw “/api/v1/nodes/(your-node-name)/proxy/stats/summary” There is also this kubectl get –raw “/api/v1/nodes/(your-node-name)/proxy/metrics/cadvisor”” EDIT: I’ve created a Prometheus exporter for this now. https://github.com/jmcgrath207/k8s-ephemeral-storage-metrics