Set configuration context $ kubectl config use-context wk8s
configure the kubelet systemed managed service, on the node labelled with name=wk8s-node-1,to launch a pod containing a single container of image nginx named myservice automatically.
Any spec file requried should be placed in the /etc/kuberneteds/mainfests directory on the node
Hints:
You can ssh to the failed node using $ ssh wk8s-node-0
You can assume elevated privileges on the node with the following command $ sudo -i
请给出操作步骤。
切换至wk8s上下文:
kubectl config use-context wk8s
查看有labelname=wk8s-node-1
的node的信息
kubectl get nodes -l name=wk8s-node-1 -o wide
登录指定的机器,并获得操作权限。
ssh wk8s-node-0
sudo -i
查看kubelet服务启动参数--config
systemctl status kubelet -l
在--config指定的文件中,找到staticPodPath文件目录
# cat /var/lib/kubelet/config.yaml|grep staticPodPath
staticPodPath: /etc/kubernetes/manifests
在静态pod目录下创建yaml,使用下面命令生成符合要求的myservice.yaml,等待kubelet自动拉起静态pod
kubectl run myservice --image=nginx --generator=run-pod/v1 --dry-run -o yaml > myservice.yaml
context相关操作官方命令指南: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#config
Create static Pods官网说明: https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/
本题主要考kubelet的配置,以及Static Pod的创建。
可以通过systemctl status kubelet -l
查看kubelet进程的配置文件路径。
在这里插入图片描述
以及通过配置文件config.yaml
找到staticPodPath
。
在这里插入图片描述
有时候,情况可能会不一样,systemctl status kubelet -l
查到的10-kubeadm.conf
中没有config.yaml
配置:
在这里插入图片描述
而是将其直接用--pod-manifest-path
传入,所以这种情况就需要修改10-kubeadm.conf
中的配置路径(如果路径不是期望路径)
--pod-manifest-path=/etc/kubernetes/manifests
修改后需要重启kubelet:
systemctl start kubelet
Set configuration context $ kubectl config use-context k8s; Create a deployment as follows; Name: nginx-dns; Exposed via a service: nginx-dns; Ensure that the service & pod are accessible via their respective DNS records; The container(s) within any pod(s) running as a part of this deployment should use the nginx image; Next,use the utiliity nslookup to look up the DNS records of the service & pod and write the output to /opt/service.dns and /opt/pod.dns respectively; Ensure you use the busybox:1.28 image (or earliser) for any testing, an the latest release has an unpstream bug which impacts the use of nslookup;
• end •