当前位置：首页 > news >正文

k8s字段

news 2026/4/15 10:11:59

1、创建pod字段

1、node亲和性字段

apiVersion: v1
kind: Pod
metadata:name: pod1namespace: dev
spec:affinity:nodeAffinity:preferredDuringSchedulingIgnoredDuringExecution:- weight: 80preference:matchExpressions:- key: aoperator: In  #键的值必须在给定的列表中，exists节点必须存在这个值，不管它的值是什么values:- bcontainers:- name: pod1image: docker.io/library/tomcat:8.5-jre8-alpineimagePullPolicy: IfNotPresent

2、控制器字段

1、deployment字段

apiVersion:
kind:
metadata:
spec:replicas: #副本数量minReadySeconds: #默认是0,创建pod之后过几秒后升级selector:matchlabels:strategy：type: RollingUpdate滚动更新或者Recreate重建更新 rollingUpdate：  #更新策略maxSurge：#允许超过指定副本数量几个。默认是25%，5*25%=1.25当2个，maxUnavailable: #更新过程中，允许几个pod不能用，目标5，这个为1哥不能用， 至少有4个可以用template: #定义pod模版metadata:labels:spec:containers:- name:

2、rs字段

[root@master rs]# cat rs.yaml 
apiVersion: apps/v1
kind: ReplicaSet
metadata:name: rs1namespace: ziduan
spec:replicas: 3selector:matchLabels:rs1: pod1template:metadata:labels:rs1: pod1spec:containers:- name: nginximage: docker.io/library/nginx:1.9.1imagePullPolicy: IfNotPresent

3、statefulset字段

有顺序的，并且这个控制器创建的pod有唯一的dns,其他都没有dns
访问这个svc返回的是pod的ip和dns
其他的服务的话，返回的是服务的dns和ip

[root@master kongzhiqi]# cat statefulset.yaml 
apiVersion: apps/v1
kind: StatefulSet
metadata:name: state1namespace: ziduan
spec:replicas: 2selector:matchLabels:state1: d1serviceName: nginx  #无头服务template:metadata:labels:state1: d1spec:containers:- name: nginximage: docker.io/library/tomcat:8.5-jre8-alpineimagePullPolicy: IfNotPresent
---
apiVersion: v1
kind: Service
metadata:name: nginx namespace: ziduan
spec:clusterIP: Nonetype: ClusterIPselector:state1: d1ports:- name: p1port: 8080targetPort: 8080

4、daemonset字段

每个节点只有一个存在

[root@master kongzhiqi]# cat daemonset.yaml 
apiVersion: apps/v1
kind: DaemonSet
metadata:name: daemon1namespace: ziduan
spec:selector:matchLabels:daemon: d1template:metadata:labels:daemon: d1spec:containers:- name: state1image: docker.io/library/busybox:1.28imagePullPolicy: IfNotPresentcommand: ["/bin/sh","-c","sleep 360000"]

3、服务字段

1、nodeport字段

apiVersion: v1
kind: Service
metadata:name: s1-d1namespace: dev
spec:type: NodePort   #nodeport类型selector:   #服务选择器app: d1ports:   #端口- port: 80  #服务端口targetPort: 80  #目标端口nodePort: 30080  #节点端口

4、持久化存储

1、临时存储和和宿主机目录和nfs

#临时存储
apiVersion: v1
kind: Pod
metadata:name: v1namespace: dev
spec:containers:- name: v1image: docker.io/library/nginximagePullPolicy: IfNotPresentvolumeMounts: #容器挂载点- mountPath: /cache name: v1volumes:  #挂载到主机上面的目录- name: v1emptyDir: {} #空目录#宿主机目录
apiVersion: v1
kind: Pod
metadata:name: v2namespace: dev
spec:containers:- name: v2image: docker.io/library/nginximagePullPolicy: IfNotPresentvolumeMounts:- name: v2mountPath: /cachevolumes:- name: v2hostPath:type: DirectoryOrCreate  #不存在的创建path: /data1#nfs作为存储
[root@master data]# exportfs -arv
exporting *:/data/v4
[root@master data]# cat /etc/exports
/data/v4 *(rw)apiVersion: v1
kind: Pod
metadata:name: v4namespace: dev
spec:containers:- name: v4image: docker.io/library/nginximagePullPolicy: IfNotPresentvolumeMounts:- name: v4mountPath: /cachevolumes:- name: v4nfs:path: /data/v4  #nfs存储server: 192.168.200.100  #服务器ip地址

2、pv和pvc字段

#创建pv,后端存储nfs作为pv
apiVersion: v1
kind: PersistentVolume
metadata:name: v3namespace: dev
spec:capacity:storage: 1GiaccessModes:- ReadWriteOncenfs:path: /data/v3server: 192.168.200.100#创建pvc
apiVersion: v1
kind: PersistentVolumeClaim
metadata:name: v3-pvcnamespace: dev
spec:accessModes: #访问模式- ReadWriteOnceresources: #pvc的需求requests:storage: 2Gi#pod以pvc使用
[root@master volumes]# cat pod1.yaml 
apiVersion: v1
kind: Pod
metadata:name: p1namespace: dev
spec:containers:- name: p1image: docker.io/library/nginximagePullPolicy: IfNotPresentvolumeMounts:- name: p1mountPath: /cachevolumes:- name: p1persistentVolumeClaim:  #使用pvc作为存储claimName: v3-pvc  #pvc作为存储

5、hpa字段

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:name: hpa-testnamespace: test
spec:minReplicas: 1maxReplicas: 20behavior:   #精细化的定义伸缩策略scaleUp:policies:- periodSeconds: 3  #最多每3秒的时间内增加5个podtype: pods  3 #伸缩政策的类型，基于pod，percent基于百分比，value基于绝对值缩放value: 5metrics:   #定义监控指标的- resource: #仅当type为resource时，监控的资源name: cpu  #监控资源的名称，cpu或者memorytarget:  #监控资源的目标值，type: Utilization  #使用率，通常用于cpus, AverageValue 表示要达到平均值，用于memoryaverageUtilization: 20  #资源请求值的百分比type: Resource  #基于cpu或者内存，pod基于数量的指标scaleTargetRef:apiVersion: apps/v1kind: Deploymentname: hpa-1

6、rbac的字段

1、角色和角色绑定

[root@master rbac]# cat role.yaml 
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:name: r1namespace: ziduan
rules:
- apiGroups: ["*"] # 这个apiversionresources: ["pods"] # 资源的名称，pod,deploymentverbs: ["list"]  # 能进行的操作---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:name: r1-bindingnamespace: ziduan
roleRef:apiGroup: rbac.authorization.k8s.iokind: Role  # 绑定的角色的名称name: r1[root@master rbac]# cat role.yaml 
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:name: r1namespace: ziduan
rules:
- apiGroups: ["*"]resources: ["pods"]verbs: ["list"]---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:name: r1-bindingnamespace: ziduan
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: r1
subjects:
- apiGroup: rbac.authorization.k8s.io kind: User  # 如果是serviceaccount的话，apigroup就是""这个了name: q1

查看全文

http://www.jsqmd.com/news/638661/