经验总结

  1. 首页 > 生活 > >

七 pod：静态pod( 三 )

生活百科pod(七)：静态pod

查看pod
[root@k8scloude1 pod]# kubectl get pods -n podNAMEREADYSTATUSRESTARTSAGEpod-k8scloude21/1Running06s3.2.2 静态pod默认目录/etc/kubernetes/manifests注意：进行这一步的时候 ， 先还原kubelet配置文件/usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf
查看配置文件 ， 可以发现静态pod默认目录为/etc/kubernetes/manifests
【七 pod：静态pod】[root@k8scloude2 kubelet.d]# cat /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf# Note: This dropin only works with kubeadm and kubelet v1.11+[Service]Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamicallyEnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.EnvironmentFile=-/etc/sysconfig/kubeletExecStart=ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS[root@k8scloude2 kubelet.d]# ls /var/lib/kubelet/config.yaml/var/lib/kubelet/config.yaml[root@k8scloude2 kubelet.d]# cat /var/lib/kubelet/config.yaml | grep manifeststaticPodPath: /etc/kubernetes/manifests#默认的静态pod的目录为 ls /etc/kubernetes/manifests[root@k8scloude2 kubelet.d]# ls /etc/kubernetes/manifests在默认的静态pod目录/etc/kubernetes/manifests/下创建pod yaml文件
#namespace: pod:指定pod的命名空间[root@k8scloude2 kubelet.d]# vim ~/pod.yaml [root@k8scloude2 kubelet.d]# cat ~/pod.yamlapiVersion: v1kind: Podmetadata:creationTimestamp: nulllabels:run: podname: podnamespace: podspec:containers:- image: nginximagePullPolicy: IfNotPresentname: podresources: {}ports:- name: httpcontainerPort: 80protocol: TCPdnsPolicy: ClusterFirstrestartPolicy: Alwaysstatus: {}[root@k8scloude2 kubelet.d]# cp ~/pod.yaml /etc/kubernetes/manifests/可以发现 ， 静态pod已经创建了
[root@k8scloude1 pod]# kubectl get pods -n podNAMEREADYSTATUSRESTARTSAGEpod-k8scloude21/1Running06s删除yaml文件 ， 静态pod消失
#删除yaml文件[root@k8scloude2 kubelet.d]# rm -rf /etc/kubernetes/manifests/pod.yaml #pod消失[root@k8scloude1 pod]# kubectl get pods -n podNo resources found in pod namespace.前面几步 ， 静态pod是在k8s集群的worker节点上做的 ， 现在在k8s集群的master节点上做 。
注意：如果在/usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf里添加了--pod-manifest-path=/etc/kubernetes/kubelet.d ， 则相应的/etc/kubernetes/manifests/下的yaml文件也要移动到/etc/kubernetes/kubelet.d目录下 ， 不然k8s集群的master节点启动不起来 。
可以看到k8s集群的master节点有很多静态pod 。
[root@k8scloude1 pod]# ls /etc/kubernetes/manifests/etcd.yamlkube-apiserver.yamlkube-controller-manager.yamlkube-scheduler.yaml

经验总结扩展阅读


上一篇：文科生什么专业就业前景好 哪些专业吃香

下一篇：糖尿病人能吃广式腊肠吗 广式腊肠放了糖吗