k8s
Section: (pj)
Updated: 2025-07-25
Index
Return to Main Contents
kubectl -context=staging get nodes
kubectl -context=staging get pods
Show secrets:
kubectl get secrets -all-namespaces kubectl get secret
the-secret-name -o jsonpath=`{.data}' | jq kubectl get secret
the-secret-name -o jsonpath=`{.data.foo}' | base64 -decode
Get pods matching a label:
kubectl get pods -l app=foo
Debugging pods:
This is a useful image for debugging problems:
k debug mypod -it -image=nicolaka/netshoot
If you want to see the same disk contents (image+volumes), make a copy
of the pod with a different entrypoint command:
k debug mypod -it -copy-to=debug -c thecontainer - bash
For k3s
Lots of details:
-
sudo k3s check-config
To stop all the containers (since sudo systemctl stop k3s
doesn't do it, per https://github.com/k3s-io/k3s/issues/2583):
-
sudo /usr/local/bin/k3s-killall.sh
This is good if you're trying to give the ports back to an nginx
running on the host.
To move pods from one node group to another:
The goal is to launch pods on the new nodes before killing the
pods on the old nodes.
- •
-
Create the new node group.
Wait until the nodes are ready.
- •
-
Taint the old nodes so no new pods will get scheduled there:
-
k taint nodes ip-10-10-245-95.ec2.internal key1=value1:NoSchedule
- •
-
Scale the deployment to launch new pods, which should all get scheduled
on the new nodes:
-
k scale deployment --replicas=2 -n foo bar
- •
-
Drain the old nodes:
-
k drain ip-10-10-245-95.ec2.internal --ignore-daemonsets --delete-emptydir-data
- •
-
Scale down:
-
k scale deployment --replicas=1 -n foo bar
AUTHORS
Paul A. Jungwirth.
Index
- Show secrets:
-
- Get pods matching a label:
-
- Debugging pods:
-
- For k3s
-
- To move pods from one node group to another:
-
- AUTHORS
-
This document was created by
man2html,
using the manual pages.
Time: 21:16:02 GMT, January 04, 2026