kubernetes pod vs deployment

node nodes[[emailprotected] ~]# yum -y install flannel kubernetes-node2. Modify the Flannel configuration file[[emailprotected] ~]# cat /etc/sysconfig/flanneld | grep -v "^#" | grep -v "^$"FLANNEL_ETCD_ENDPOINTS="http://192.168.10.131:2379"FLANNEL_ETCD_PREFIX="/atomic.io/network"3. Modify the Kubernetes configuration file[[emailprotected] ~]# cat /etc/kubernetes

container Ansible role How to use please read the following article Ansible Role "How to use?" 】 Cluster installation methodInstall kubernetes ha high availability cluster in static pod mode.Ansible Managing node OperationsOS:CentOS Linux release 7.4.1708 (Core)Ansible2.5.3Installing Ansible# yum -y install ansible# ansible --versionansible 2.5.3 config file = /etc/ansib

0. PrefaceOverall architecture directory: ASP. NET core distributed project-Directoryk8s Schema Catalog: Kubernetes (K8S) cluster deployment (K8S Enterprise Docker container cluster Management) series catalogfirst, server settings1. Set the selinux of each server to disabledHow to set it up:Vi/etc/selinux/configWill selinux=disabled, then save, and then execute the command: Setenforce 0, make it effective.2

Pictured in San Francisco Pier 7:coit Tower The last time we introduced the Kubernetes deployment Fabric (clickable) of the overall architecture and network, storage planning, this issue is serialized second, detailing the deployment tool design details, including template customization and configuration settings. A PDF version of this method is attached. 3. De

=-/etc/kubernetes/ Configenvironmentfile=-/etc/kubernetes/scheduleruser=kubeexecstart=/usr/bin/kube- Scheduler $KUBE _logtostderr $KUBE _log_level $KUBE _master $KUBE _scheduler_argsrestart= on-failurelimitnofile=65536[Install]wantedby=multi-user.targetThe relevant configuration file/etc/kubernetes/scheduler content is:# # # #

:{}- name:configconfigMap:name:example-redis-config items:-key: redis-configpath:redis.conf# Kubectl create-f redis-pod.yaml pod "Redis" created# kubectl exec-it redis redis-cli127.0.0.1:6379> 127.0.0.1:6379> 127.0.0.1:6379> config get maxmemory1) "Maxmem Ory "2)" 2097152 "127.0.0.1:6379> config get maxmemory-policy1)" Maxmemory-policy "2)" Allkeys-lru "127.0.0.1:6379 >8. Managing Kubernetes objects with th

: 8GivolumeMode: FilesystemaccessModes: - ReadWriteOncepersistentVolumeReclaimPolicy: RecyclemountOptions: - hard - nfsvers=4.1nfs: path: /data ##NFS服务器上的共享目录 server: 192.168.246.168 ##NFS服务器的ip地址 Create PVC##pvc的yamlapiVersion: v1kind: PersistentVolumeClaimmetadata:name: datadir-nginx-0spec:accessModes: - ReadWriteOnceresources: requests: storage: 1Giselector: matchLabels: #说明：创建PVC的名称和Deployment中的名称要对应上，要不然

/KUBERNETES.PEM \>--KEY-FILE=/ETC/KUBERNETES/SSL/KUBERNETES-KEY.PEM \> Get/kube-centos/network/config#输出{"Network": "172.30.0.0/16", "Subnetlen": "Backend": {"Type": "HOST-GW"}}#此处是查看主网络配置Etcdctl--endpoints=${etcd_endpoints}--ca-file=/etc/kubernetes/ssl/ca.pem--cert-file=/etc/kubernetes/ssl/ Kubernetes.pem--key-file=/e

.eyjpc3mioijrdwjlcm5ldgvzl3nlcnzpy2vhy2nvdw50iiwia3vizxjuzxrlcy5pby9zzxj2awnlywnjb3vu Dc9uyw1lc3bhy2uioijrdwjllxn5c3rlbsisimt1ymvybmv0zxmuaw8vc2vydmljzwfjy291bnqvc2vjcmv0lm5hbwuioijhzg1pbi11c2vylxrva2vultjkd 2z4iiwia3vizxjuzxrlcy5pby9zzxj2awnlywnjb3vudc9zzxj2awnllwfjy291bnqubmftzsi6imfkbwlulxvzzxiilcjrdwjlcm5ldgvzlmlvl3nlcnzpy2 Vhy2nvdw50l3nlcnzpy2utywnjb3vudc51awqioijmyzi4njnmzs02ntuyltexztgtywu4yi0wmdbjmjkynmu2zdmilcjzdwiioijzexn0zw06c2vydmljzwf Jy291bnq6a3vizs1zexn0zw06ywrtaw4tdxnlcij9.rrc4zp

installed to use dashboard. When the dashboard service starts, check to see if the service is working:[[emailprotected] ~]# kubectl get pod -n kube-systemNAME READY STATUS RESTARTS AGEcoredns-77c989547b-2rg9h 1/1 Running 0 2hcoredns-77c989547b-cbj5h 1/1 Running 0 2hkubernetes-dashboard-7d5dcdb6d9-h66fs 1/1 Running 0 1h[[

The previous blog has introduced the deployment of a simple kubernetes cluster, but the cluster environment does not have a reasonable network configuration. In the actual production to realize the communication of the components in the cluster, it is necessary to use the network plug-in provided by the third party.Flannel binary Installation1. Download Fannel componentswget https://github.com/coreos/flanne

] node2]# IP a|egrep "Docker|flan"3:flannel0: inet 10.1.77.0/16 Scope Global Flannel04:DOCKER0: inet 10.1.77.1/24 Scope Global DOCKER0Finally, start the Kubernetes node service:[Email protected] node2]# nohup kubelet--address=0.0.0.0 \--port=10250--logtostderr=true--v=0 \--api-servers=http://192.168.11.10:8080 >>/var/log/kubernetes/kubelet.log 2>1 [Email protected] node2]# nohup kube-proxy--logtostderr=true

Annotations:scheduler.alpha.kubernetes.io/critical-pod:"'spec:serviceAccountName:kubernetes-Dashboard Containers:-name:kubernetes-Dashboard Image:registry.docker-cn.com/kubernetesdashboarddev/kubernetes-dashboard-amd64:headresources:limits:cpu:100m memory:300mi requests:cpu:1 00m memory:100mi Ports:-Containerport:9090LivenessProbe:httpGet:path:/Port:9090Initialdelayseconds: -timeoutseconds: -tolerations:-K

, Etcd_name according to ETCD system service inside the configuration one by one corresponds, respectively is INFRA1,INFRA2,INFRA35. Set boot and start ETCDSystemctl daemon-reloadsystemctl enable etcdsystemctl start Etcdsystemctl status Etcd6, detection of cluster workAt any node, either master or node, execute the following commandEtcdctl --ca-file=/etc/kubernetes/ssl/ca.pem --cert-file=/etc/kubernetes