[root@registry work]# kubectl explain pods.spec.containers.readinessProbe[root@registry work]#   kubectl explain pods.spec.containers.livenessProbeexec  <Object>
failureThreshold  <integer>   探测成功后，最少连续探测失败多少次才被认定为失败，默认是 3httpGet <Object>
initialDelaySeconds <integer> 容器启动后第一次执行探测是需要等待多少秒
periodSeconds <integer>   执行探测的频率，默认是10秒。
successThreshold  <integer> 探测失败后，最少连续探测成功多少次才被认定为成功，默认是 1tcpSocket <Object>    
timeoutSeconds  <integer> 探测超时时间，默认1秒。
[root@master1 yaml]# cat livenessl.yaml apiVersion: v1 
kind: Pod
metadata:
  name: liveness-exec-pod 
  namespace: default 
spec:
  containers:
- name: live-ness-container 
    image: 192.168.192.234:888/nginx
    imagePullPolicy: IfNotPresent
    command: ["/bin/sh","-c","touch /tmp/healthy ;sleep 60;rm -rf /tmp/healthy; sleep 30"]
    livenessProbe:
      exec: 
        command: ["test","-e","/tmp/healthy"]
      initialDelaySeconds: 1      periodSeconds: 3[root@master1 yaml]# kubectl create -f livenessl.yaml [root@master1 yaml]# cat httpget.yaml apiVersion: v1 
kind: Pod
metadata:
  name: liveness-httpget-pod 
  namespace: default 
spec:
  containers:
- name: live-ness-container 
    image: 192.168.192.234:888/nginx
    imagePullPolicy: IfNotPresent
    livenessProbe:
      httpGet: 
        port: 80        path: /index.html
      initialDelaySeconds: 1      periodSeconds: 3[root@master1 ~]# kubectl exec -it  liveness-httpget-pod  -- /bin/bashroot@liveness-httpget-pod:/# root@liveness-httpget-pod:/usr/share/nginx/html# mv index.html index.html.bak[root@master1 yaml]# kubectl describe pods liveness-httpget-pod Events:
  Type     Reason     Age                  From               Message
-------------------------  Normal   Scheduled  5m56s                default-scheduler  Successfully assigned default/liveness-httpget-pod to master2
  Normal   Pulled     13s (x2 over 5m56s)  kubelet, master2   Container image "192.168.192.234:888/nginx" already present on machine
  Normal   Created    13s (x2 over 5m56s)  kubelet, master2   Created container live-ness-container
  Warning  Unhealthy  13s (x3 over 19s)    kubelet, master2   Liveness probe failed: HTTP probe failed with statuscode: 404  Normal   Killing    13s                  kubelet, master2   Container live-ness-container failed liveness probe, will be restarted
  Normal   Started    12s (x2 over 5m56s)  kubelet, master2   Started container live-ness-container

[root@master1 ~]# kubectl explain pods.spec.containers.readinessProbe[root@master1 yaml]# cat readness.yamlapiVersion: v1 
kind: Pod
metadata:
  name: readiness-exec-pod 
  namespace: default 
spec:
  containers:
- name: readiness-container 
    image: 192.168.192.234:888/nginx
    imagePullPolicy: IfNotPresent
    ports: 
- name: http
      containerPort: 80    livenessProbe:
      httpGet: 
        port: http 
        path: /index.html 
      initialDelaySeconds: 1      periodSeconds: 3

[root@registry work]# kubectl explain pods.spec.containers.resourcesspec.containers[].resources.limits.cpu
spec.containers[].resources.limits.memory
spec.containers[].resources.requests.cpu
spec.containers[].resources.requests.memory
[root@registry work]# cat v3.yaml apiVersion: v1
kind: Pod
metadata:
  name: nginx
spec:
  containers:
- image: nginx
      name: nginx
      resources:
        requests:
          cpu: "300m"          memory: "56Mi"        limits:
          cpu: "500m"          memory: "128Mi"#mem支持单位：Ki | Mi | Gi | Ti | Pi 等

apiVersion: v1
kind: Pod
metadata:
  name: qos
  annotations:
    kubernetes.io/ingress-bandwidth: 3M
    kubernetes.io/egress-bandwidth: 4M
spec:
  containers:
- name: iperf3
    image: networkstatic/iperf3
    command:
- iperf3
--s

[root@registry ~]# cat v3.yaml apiVersion: v1
kind: Pod
metadata:
  name: init-demo
spec:
  containers:
- name: nginx
    image: nginx
    ports:
- containerPort: 80    volumeMounts:
- name: workdir
      mountPath: /usr/share/nginx/html
  initContainers:
- name: install
    image: busybox
    command:
-wget-"-O"-"/work-dir/index.html"- http://kubernetes.io
    volumeMounts:
- name: workdir
      mountPath: "/work-dir"  dnsPolicy: Default
  volumes:
- name: workdir
    emptyDir: {}

[root@master1 ~]# kubectl get pods --show-labelsNAME                           READY   STATUS    RESTARTS   AGE     LABELS
client                         1/1     Running   0          5d23h   run=client
nginx-deloy-67f8c9dc5c-bgx9k   1/1     Running   0          5d22h   pod-template-hash=67f8c9dc5c,run=nginx-deloy
[root@master1 ~]# kubectl get pods -L=run,nginx   //输出增加run和nginx两个列、NAME                           READY   STATUS    RESTARTS   AGE     RUN           NGINX
client                         1/1     Running   0          5d23h   client        
nginx-deloy-67f8c9dc5c-bgx9k   1/1     Running   0          5d22h   nginx-deloy   
[root@master1 ~]# kubectl get pods -l pod-template-hash   //具有标签 pod-template-hash 的pod [root@master1 ~]# kubectl get pods -l run=client   //标签run为client的NAME     READY   STATUS    RESTARTS   AGE
client   1/1     Running   0          5d23h

[root@master1 ~]# kubectl label pods client name=label1,run [root@master1 ~]# kubectl label pods client name=label2 --overwrite  //强制修改标签

[root@master1 ~]#   kubectl label client client name-   //key- 即可删除标签

[root@registry ~]# kubectl explain deployment.spec.selector  matchLabels:直接给定键值
  mathExpressions:{key:"KEY",operator:"OPERATOR",value:[VAL1,VAL2,VAL3..]}
    操作符：
      In,NotIn:value字段的值必须为非空列表
      Exists,NotExists:value字段的值必须为空列表
标签的对象可以是：pods、node...
annotations:与label不同的地方在于、他不能用于挑选资源对象，仅用于对象提供“元数据”
  可以在yaml文件中定义，也可以在
[root@registry ~]# kubectl describe pods $pod_name 查看 

[root@master1 ~]# kubectl explain ReplicaSet  //kubectl explain rs[root@master1 yaml]# kubectl create -f rs.yaml replicaset.apps/myrs created
[root@master1 yaml]# cat rs.yaml apiVersion: apps/v1
kind: ReplicaSet
spec:
  replicas: 2  selector: 
    matchLabels: 
      app: myapp
      release: beta 
  template: 
    metadata:
      name: myapp-pod
      labels:
         app: myapp
         release: beta
         environment: dev
    spec:
      containers: 
- name: myrs-container
        image: 192.168.192.234:888/nginx:latest
        ports: 
- name: http 
          containerPort: 80metadata: 
  name: myrs
  namespace: default
[root@master1 yaml]# [root@master1 yaml]# kubectl get pods -l appNAME         READY   STATUS    RESTARTS   AGE
myrs-fnhwd   1/1     Running   0          61s
myrs-x5zgh   1/1     Running   0          61s

[root@master1 yaml]# kubectl get pods --show-labelsNAME                           READY   STATUS    RESTARTS   AGE     LABELS
client                         1/1     Running   0          10d     run=client
liveness-httpget-pod           1/1     Running   1          4d      <none>
myrs-fnhwd                     1/1     Running   0          5m5s    app=myapp,environment=dev,release=beta
myrs-x5zgh                     1/1     Running   0          5m5s    app=myapp,environment=dev,release=beta
nginx-deloy-67f8c9dc5c-bgx9k   1/1     Running   0          10d     pod-template-hash=67f8c9dc5c,run=nginx-deloy
readiness-exec-pod             1/1     Running   0          3d23h   <none>
[root@master1 yaml]# kubectl label pods liveness-httpget-pod app=myapp release=beta  --overwritepod/liveness-httpget-pod labeled
[root@master1 ~]# kubectl get pods  --show-labels -l app,release  //发现myrs被干掉一个NAME                   READY   STATUS    RESTARTS   AGE     LABELS
liveness-httpget-pod   1/1     Running   1          4d      app=myapp,release=beta
myrs-x5zgh             1/1     Running   0          7m28s   app=myapp,environment=dev,release=beta

[root@registry ~]# cat v3.yaml apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
  name: frontend-scaler
spec:
  scaleTargetRef:
    kind: ReplicaSet
    name: frontend
  minReplicas: 3  maxReplicas: 10  targetCPUUtilizationPercentage: 50

[root@registry ~]# kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1[root@registry ~]# kubectl edit deployment/nginx-deployment[root@registry ~]# kubectl rollout status deployment/nginx-deployment   #查看 rollout 的状态，只要执行Deployment 可以保证在升级时只有一定数量的 Pod 是 down 的。默认的，它会确保至少有比期望的Pod数量少一个是up状态（最多一个不可用）。
Deployment 同时也可以确保只创建出超过期望数量的一定数量的 Pod。默认的，它会确保最多比期望的Pod数量多一个的 Pod 是 up 的（最多1个 surge ）。
[root@registry work]# kubectl describe deployment $deployment_名称 RollingUpdateStrategy:  1 max unavailable, 25% max surge  #查看更新策略

[root@master1 ~]# kubectl get pods --show-labels -l version -w [root@master1 ~]# kubectl apply -f deployment.yaml deployment.apps/dpv1 configured
查看image更新生效
[root@master1 ~]# kubectl describe pods $pods [root@master1 ~]# kubectl get rs -o wide NAME              DESIRED   CURRENT   READY   AGE   CONTAINERS       IMAGES                            SELECTOR
dpv1-5778f9d958   222       11m   mydp             192.168.192.234:888/nginx:v2       name=mydp,pod-template-hash=5778f9d958,version=dpv1
dpv1-7b7df4f86c   000       26m   mydp             192.168.192.234:888/nginx:latest   name=mydp,pod-template-hash=7b7df4f86c,version=dpv1
可以看到保存了2个模板，一个为0，一个为2
[root@master1 yaml]# kubectl rollout history deployment dpv1   //查看版本历史deployment.extensions/dpv1 
REVISION  CHANGE-CAUSE
1         <none>
2         <none>

[root@master1 yaml]# kubectl patch deployment dpv1 -p ‘{“spec”:{“replicas”:5}}’deployment.extensions/dpv1 patched

[root@master1 yaml]# cat daemon.yaml [root@registry prometheus]# cat node-exporter-ds.yml apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: node-exporter
  namespace: kube-system
  labels:
    k8s-app: node-exporter
    kubernetes.io/cluster-service: "true"    addonmanager.kubernetes.io/mode: Reconcile
    version: v0.15.2
spec:
  selector:
    matchLabels:
      k8s-app: node-exporter
      version: v0.15.2
  updateStrategy:
    type: OnDelete
  template:
    metadata:
      labels:
        k8s-app: node-exporter
        version: v0.15.2
      annotations:
        scheduler.alpha.kubernetes.io/critical-pod: ''    spec:
      priorityClassName: system-node-critical
      containers:
- name: prometheus-node-exporter
          image: "prom/node-exporter:v0.15.2"          imagePullPolicy: "IfNotPresent"          args:
---path.procfs=/host/proc
---path.sysfs=/host/sys
          ports:
- name: metrics
              containerPort: 9100              hostPort: 9100          volumeMounts:
- name: proc
              mountPath: /host/proc
              readOnly:  true- name: sys
              mountPath: /host/sys
              readOnly: true          resources:
            limits:
              cpu: 10m
              memory: 50Mi
            requests:
              cpu: 10m
              memory: 50Mi
      hostNetwork: true      hostPID: true      volumes:
- name: proc
          hostPath:
            path: /proc
- name: sys
          hostPath:
            path: /sys
[root@registry prometheus]# kubectl explain daemonset.specupdateStrategy  #Pod更新策略template  #Pod模板selector  #node标签选择器，根据matchExpressions,matchLabelsrevisionHistoryLimit  #历史保留个数minReadySeconds #最少多少秒必须保证可用

[root@registry work]# cat v3.yaml apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nginx
spec:
  selector:
    matchLabels:
      name: nginx
      department: dev
  replicas: 2  template:
    metadata:
      name: nginx
      labels:
        name: nginx
        department: dev
    spec:
      containers:
- name: nginx
        image: 192.168.192.234:888/nginx:latest
        imagePullPolicy: IfNotPresent
      restartPolicy: Always
---apiVersion: v1
kind: Service
metadata:
  name: test-nginx
spec:
  ports: 
- name: http
    port: 8080    targetPort: 80    protocol: TCP
- name: ssh    port: 2222    targetPort: 22    protocol: TCP
  selector:
    name: nginx
    department: dev
  type: ClusterIP

[root@registry work]# kubectl explain svc.specclusterIP  #服务ip，集群内有效externalIPs  #引入外部的IPhealthCheckNodePort #健康检查端口ports  #nodePort使用node的端口,port服务端口,targetPort pod端口selector #标签选择器type #服务类型 ExternalName, ClusterIP, NodePort, and LoadBalancer  ExternalName:集群外部的服务引用到集群内部使用
  ClusterIP:集群内使用
  NodePort:物理机网段

[root@master1 ~]# kubectl run nginx-deloy --image=192.168.192.234:888/nginx:latest --port=80 --replicas=1[root@master1 ~]# kubectl get pods -o wide   //该pod在Replicas和Deployment中都可以看到，describe 的controlled by ReplicasNAME                           READY   STATUS    RESTARTS   AGE    IP            NODE      NOMINATED NODE   READINESS GATES
nginx-deloy-67f8c9dc5c-4nk68   1/1     Running   0          3m5s   172.30.72.3   master1   <none>           <none>

Usage:
  kubectl expose (-f FILENAME | TYPE NAME) [--port=port] [--protocol=TCP|UDP|SCTP] [--target-port=number-or-name]
[--name=name] [--external-ip=external-ip-of-service] [--type=type] [options]  
--type='': Type for this service: ClusterIP, NodePort, LoadBalancer, or ExternalName. Default is 'ClusterIP'.
   (-f FILENAME | TYPE NAME)  //TYPE:控制器类型 NAME:控制器名称，expose之后 service提供一个固定的ip，但是仅限集群内部pod客户端使用

[root@master1 ~]# kubectl expose deployment nginx-deloy  --name nginx1 --port=80 --target-port=80  --protocol=TCP service/nginx1 exposed
[root@master1 ~]# kubectl get servicesNAME          TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
dnsutils-ds   NodePort    10.254.98.197   <none>        80:31707/TCP   2d5h
kubernetes    ClusterIP   10.254.0.1      <none>        443/TCP        2d9h
my-nginx      ClusterIP   10.254.1.216    <none>        80/TCP         2d5h
nginx1        ClusterIP   10.254.63.79    <none>        80/TCP         11s

[root@client /home/admin]
#cat /etc/resolv.conf nameserver 10.244.0.2
search default.svc.cluster.local svc.cluster.local cluster.local
options ndots:5
  //client机器内ping nginx1会自动补全 nginx1.default.svc.cluster.local (10.254.63.79)，解析的地址为clusterip
[root@master1 ~]# dig -t A nginx1.default.svc.cluster.local @10.254.0.2 这种是可以的  kubectl describe service nginx //可以看到实际的情况
  kubectl get pods --show-labels  kubectl edit service$服务名  //可以直接修改服务信息
[root@master1 ~]# kubectl describe svc  nginx1  //删除pod后ip会发生变化，但是使用cluster ip人仍然可以访问，    //svc和pod 通过label selector 关联
Name:              nginx1
Namespace:         default
Labels:            run=nginx-deloy
Annotations:       <none>
Selector:          run=nginx-deloy   //关联 pod的标签为nginx-deploy 
Type:              ClusterIP
IP:                10.254.63.79
Port:              <unset>  80/TCP
TargetPort:        80/TCP
Endpoints:         172.30.200.3:80
Session Affinity:  None
Events:            <none>
[root@master1 ~]# kubectl get pods --show-labelsNAME                           READY   STATUS    RESTARTS   AGE   LABELS
client                         1/1     Running   0          24m   run=client
nginx-deloy-67f8c9dc5c-zpv4q   1/1     Running   0          38m   pod-template-hash=67f8c9dc5c,run=nginx-deloy

[root@master1 yaml]# kubectl apply -f heaness.yaml service/headness created
[root@master1 yaml]# cat heaness.yaml apiVersion: v1
kind: Service
metadata:
  name: headness
  namespace: default
spec:
  clusterIP: ""  ports: 
- name: mysrvport 
      port: 80      targetPort: 80  selector: 
    name: mydp
    version: dpv1
[root@master1 yaml]# [root@master1 yaml]# cat heaness.yaml apiVersion: v1
kind: Service
metadata:
  name: headness
  namespace: default
spec:
  selector: 
    name: mydp
    version: dpv1
  clusterIP: "None"  ports: 
- name: mysrvport 
      port: 80      targetPort: 80[root@master1 yaml]# kubectl get svcNAME          TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
dnsutils-ds   NodePort    10.254.98.197   <none>        80:31707/TCP   12d
headness      ClusterIP   None            <none>        80/TCP         9s   //这里一定要是"None"kubernetes    ClusterIP   10.254.0.1      <none>        443/TCP        13d
mysvc         ClusterIP   10.254.0.88     <none>        80/TCP         38m
[root@master1 yaml]# dig -t A headness.default.svc.cluster.local  @172.30.200.2  //可以获取三个地址headness.default.svc.cluster.local. 5 IN A  172.30.72.6
headness.default.svc.cluster.local. 5 IN A  172.30.56.4
headness.default.svc.cluster.local. 5 IN A  172.30.200.3
[root@master1 yaml]# dig -t A mysvc.default.svc.cluster.local  @172.30.200.2  //有clusterip的只会被解析会clusterip mysvc.default.svc.cluster.local. 5 IN A 10.254.0.88

[root@registry work]# cat job.yaml apiVersion: batch/v1
kind: Job
metadata:
  name: pi
spec:
  completions: 2  parallelism: 3  template:
    metadata:
      name: nginx
    spec:
      containers:
- name: nginx
        image: "192.168.192.234:888/nginx:latest"        command: ["sh","-c","echo test for nginx &&  sleep 5"]
      restartPolicy: Never

[root@registry work]# cat cronjob.yaml apiVersion: batch/v2alpha1
kind: CronJob
metadata:
  name: hello
spec:
  schedule: "*/1 * * * *"  jobTemplate:
    spec:
      template:
        spec:
          containers:
- name: hello
            image: 192.168.192.234:888/nginx:latest
            args:
- /bin/sh
--c- date; echo Hello from the Kubernetes cluster && sleep5          restartPolicy: OnFailure

[root@master1 merged]# kubectl exec -it nginx-587764dd97-29n2g  -- ls -l /run/secrets/kubernetes.io/serviceaccounttotal 0lrwxrwxrwx 1 root root 13 Aug  910:02 ca.crt -> ..data/ca.crt
lrwxrwxrwx 1 root root 16 Aug  910:02 namespace -> ..data/namespace
lrwxrwxrwx 1 root root 12 Aug  910:02 token -> ..data/token

[root@master1 yaml]# kubectl explain pods.spec.containers [root@master1 yaml]# kubectl explain pods.spec.containers.envFrom  可以是configMap  configMapRef
  prefix
  secretRef
[root@master1 yaml]# kubectl explain pods.spec.containers.env.valueFrom  configMapKeyRef  使用configmap
  fieldRef  字段，可以是pod自身的字段，比如:metadata.name,metadata.namespace....
  resourceFieldRef  
  secretKeyRef secret 

[root@master1 yaml]# kubectl create configmap nginx-configmap --from-literal=nginx_port=80 --from-literal=server_name=www.mt.com [root@master1 configmap]# kubectl create configmap configmap-1 --from-file=www=./www.conf configmap/configmap-1 created
[root@master1 configmap]# cat www.conf server {
  server_name www.mt.com;
  listen  80;
  root /data/web/html;
}
[root@master1 configmap]# kubectl create configmap special-config --from-file=config/  #从目录创建[root@master1 configmap]# kubectl describe configmap configmap-1  #查看

[root@registry work]# cat configmap.yaml apiVersion: v1
kind: Pod
metadata:
  name: test-nginx
spec:
  containers:
- name: test-container
      image: 192.168.192.234:888/nginx:latest
      env:
- name: pod-port #这个name为pod内环境变量，引用的是nginx-configmap.nginx_port这个变量          valueFrom:
            configMapKeyRef:
              name: nginx-configmap #引用的nginx-configmap这个configmap的nginx_port这个变量              key: nginx_port
              optional: True  #是否为可选- name: pod_name
          valueFrom:
            configMapKeyRef:
              name: nginx-configmap
              key: server_name
      envFrom:  #引用的configmap，可设置多个，将引用nginx-configmap的所有内容- configMapRef:
            name: nginx-configmap
  restartPolicy: Never

[root@master1 configmap]# kubectl edit configmap nginx-configmap[root@master1 configmap]# kubectl describe configmap nginx-configmap  会发现已经修改但是pod内的仍然没有改变，环境变量方式只在系统启动时生效。存储卷方式

[root@master1 configmap]# kubectl apply -f conf2.yaml [root@master1 configmap]# cat conf2.yamlapiVersion: v1
kind: Pod
metadata:
  name: pod-cm1
  namespace: default
  labels: 
    app: cm1
    release: centos
  annotations:
    www.mt.com/created-by: "mt"spec:
  containers:
- name: pod-cm1
    image: 192.168.192.225:80/csb-broker:latest
    ports:
- name:
      containerPort: 80    volumeMounts:
- name: nginxconf
      mountPath: /etc/nginx/config.d/
      readOnly: True 
  volumes:
- name: nginxconf
    configMap:
      name: configmap-1
[root@pod-cm2 /home/admin]
#cat /etc/nginx/config.d/nginx_port 8080[root@pod-cm2 /home/admin]
#cat /etc/nginx/config.d/server_name www.mt.com

[root@master1 configmap]# kubectl explain pods.spec.volumes.configMap

[root@master1 configmap]# kubectl create secret Create a secret using specified subcommand.
Available Commands:
  docker-registry Create a secret for use with a Docker registry //连接私有仓库需要的认证信息
  generic         Create a secret from a local file, directory or literal value  
  tls             Create a TLS secret  //秘钥信息
[root@master1 configmap]# kubectl create secret generic mysql-root-password --from-literal=password=password123secret/mysql-root-password created
[root@master1 configmap]# kubectl get secret mysql-root-passwordNAME                           TYPE                                  DATA   AGE
mysql-root-password            Opaque                                1      8s
[root@master1 configmap]# kubectl describe secret mysql-root-password[root@master1 configmap]# kubectl get secret mysql-root-password -o yamlapiVersion: v1
data:
  password: cGFzc3dvcmQxMjM=  //base64编码;echo cGFzc3dvcmQxMjM= | base64 -d 解码
kind: Secret
metadata:
  creationTimestamp: "2019-07-05T08:55:48Z"  name: mysql-root-password
  namespace: default
  resourceVersion: "2794776"  selfLink: /api/v1/namespaces/default/secrets/mysql-root-password
  uid: af3180b4-9f02-11e9-8691-00163e000bdd
type: Opaque

[root@registry ~]# kubectl create secret docker-registry myregistrykey --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD