I first check the hosts for any potential cues of containerization and/or any other nodes on the network. You can also try running the binary capsh. If it exists, this can be used to print current container capabilities.
cat /etc/hosts #check for container id leik 8u9ru98432
capsh --print #check current unix capabilites
ls -l /proc/*/ns #list proc
ls -al /dev/ | grep disk #check for disks
kubectlversion#Get client and server versionkubectlgetpodkubectlgetserviceskubectlgetdeploymentkubectlgetreplicasetkubectlgetsecretkubectlgetallkubectlgetingresskubectlgetendpoints#kubectl create deployment <deployment-name> --image=<docker image>kubectlcreatedeploymentnginx-deployment--image=nginx#Access the configuration of the deployment and modify it#kubectl edit deployment <deployment-name>kubectleditdeploymentnginx-deployment#Get the logs of the pod for debbugging (the output of the docker container running)#kubectl logs <replicaset-id/pod-id>kubectllogsnginx-deployment-84cd76b964#kubectl describe pod <pod-id>kubectldescribepodmongo-depl-5fd6b7d4b4-kkt9q#kubectl exec -it <pod-id> -- bashkubectlexec-itmongo-depl-5fd6b7d4b4-kkt9q--bash#kubectl describe service <service-name>kubectldescribeservicemongodb-service#kubectl delete deployment <deployment-name>kubectldeletedeploymentmongo-depl#Deploy from config filekubectlapply-fdeployment.yml