You have not specified how you deployed kube dns but with microk8s it’s recommended to use core dns. You should not deploy kube dns or core dns on your own; rather you need to enable dns using this command microk8s enable dns which would deploy core DNS and set up DNS.
Use below command to get name and image: kubectl get pods -Ao jsonpath=”{range .items[*]}{@.metadata.name}{” “}{@.spec.template.spec.containers[].image}{“\n”}{end}” It will give output like below: name image
Use kubectl describe pod <name> to see more info
You can exec into a pod using the deployment You can use the following command: kubectl exec -it deploy/<deployment-name> — bash
When I used calico as CNI and I faced a similar issue. The container remained in creating state, I checked for /etc/cni/net.d and /opt/cni/bin on master both are present but not sure if this is required on worker node as well. root@KubernetesMaster:/opt/cni/bin# kubectl get pods NAME READY STATUS RESTARTS AGE nginx-5c7588df-5zds6 0/1 ContainerCreating 0 21m … Read more
I think you are mentioning these fields. https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/core/types.go#L2081-L2088 You can define stdin and tty in yaml file. apiVersion: v1 kind: Pod metadata: name: test spec: containers: – name: test image: test stdin: true tty: true