daemonset 和 service服務

1.nodeport 和ClusterIP

apiVersion: v1
kind: Service
#apiVersion: v1
#kind: Servive
metadata:
  name: nginx-svc
  namespace: default
spec:
  type: NodePort
  #定義類型為NodePort
  selector:
  #標簽選擇,把需要轉發的后端的標簽寫在下面
    app: nginx
  ports:
  - port: 80
    #service端口
    targetPort: 80
    #容器端口
    nodePort: 30080
    #node端口，如果是ClusterIP的這段不需要，也可以不填會隨機
---
apiVersion: v1
kind: Pod
metadata:
  name: ng1
  labels:
    app: web
spec:
  containers:
    - name: ng1
      image:  hub.c.163.com/library/nginx
      imagePullPolicy: IfNotPresent

nodeport 和ClusterIP 用法差不多就類型填的不一樣，還有ClusterIP不用填nodePort

Deployment控制器

apiVersion: v1
kind: Service
metadata:
name: nginx-svc
namespace: default
spec:
type: NodePort
#定義類型為NodePort
selector:
#標簽選擇,把需要轉發的后端的標簽寫在下面
    app: web
ports:
- port: 90
    #service端口
    targetPort: 80
    #容器端口
    nodePort: 30080
    #node端口，如果是ClusterIP的這段不需要，也可以不填會隨機
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx
spec:
replicas: 2
#表示啟動兩個容器
selector:
    matchLabels:
            app: nginx
#匹配標簽
template:
#這下面的和pod寫法一樣
    metadata:
        labels:
            app: nginx
    spec:
        containers:
        - name: ng1
            image:  hub.c.163.com/library/nginx
            imagePullPolicy: IfNotPresent

2.daemonset控制器和service無頭服務

apiVersion: apps/v1
kind: DaemonSet
#控制器類型dae...,這種控制器會把每一個node的節點都啟動一個下面標簽匹配的容器,有污點的除外
metadata:
  name: nginx-daemonset
  namespace: default
spec:
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: "ikubernetes/myapp:v1"
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-service
  namespace: default
spec:
  selector:
    app: nginx
  clusterIP: None
  ports:
  - port: 80
    targetPort: 80

service的無頭服務適用于有些服務直接要和后端的容器建立連接場景使用的

[root@cs25 ~]# kubectl get pod  -l app=myapp -o wide
NAME                            READY   STATUS    RESTARTS   AGE   IP               NODE   NOMINATED NODE   READINESS GATES
myapp-deploy-6c7db749dd-4kjdh   1/1     Running   0          31m   192.168.94.170   cs27   <none>           <none>
myapp-deploy-6c7db749dd-x95d6   1/1     Running   0          31m   192.168.100.2    cs25   <none>           <none>
#查看兩個后端容器的ip

[root@cs25 ~]# dig nginx-service.default.svc.cluster.local

; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> nginx-service.default.svc.cluster.local
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16814
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nginx-service.default.svc.cluster.local. IN A

;; ANSWER SECTION:
nginx-service.default.svc.cluster.local. 30 IN A 192.168.100.47
nginx-service.default.svc.cluster.local. 30 IN A 192.168.94.168

;; Query time: 4 msec
;; SERVER: 192.168.100.37#53(192.168.100.37)
;; WHEN: 一 12月 23 14:03:19 CST 2019
;; MSG SIZE  rcvd: 178
#解析域名  nginx-service.default.svc.cluster.local 看是不是解析的容器ip，上面可以看到兩個容器的ip都被解析到了，
#如果這邊是service帶ip就會解析成service ip由service代理至后端容器，無頭服務就是直接解析后端容器ip直接和容器建立連接。