traefik-ingress-controller labels: app: traefik spec: selector: matchLabels: app: traefik template: metadata: name: traefik labels: app: traefik Step2: 配置 service (nodeport) vi nodeport.yaml apiVersion: v1 kind: Service metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kubernetes-dashboard --key=tls.key Step6: 重新配置 service vi service.yaml apiVersion: v1 kind: Service metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kubernetes-dashboard

Deployment metadata: name: nginx-deployment spec: replicas: 3 template: metadata: labels: app: nginx spec: 06-理解K8s对象 21 containers: - name: nginx bjects/ 06-理解K8s对象 22 名称 Kubernetes REST API中的所有对象都会被Name和UID明确标识。 对于⽤户提供⾮唯⼀属性，Kubernetes提供 labels 和 annotations 来标识。 名称（Name） 名称通常由客户提供。对于给定类型的对象，⼀次只有⼀个对象可以有⼀个给定的名称（即：它们在空间上是唯⼀ 的）。但是，如果您删除⼀个对 quota ）。 在未来的Kubernetes版本中，同⼀Namespace中的对象默认有相同的访问控制策略。 没有必要使⽤多个Namespace来分隔稍微不同的资源，例如同⼀软件的不同版本，可使⽤ labels 来区分同⼀ Namespace中的资源。 使⽤Namespace Namespace的创建和删除在 Admin Guide documentation for namespaces 有描述。

apiVersion: v1 kind: Pod metadata: name: pod-nginx-web1-v1.19.5 #pod名，这个名称可带小数点 labels: #给pod打标签，便于其他资源对它的选择 lbname: lbvalue-nginx-web1 spec: #删除标签，标签名后加个减号 ★查看结点标签 # kubectl get nodes --show-labels #查看所有结点标签 # kubectl get nodes k8s-node01 --show-labels #查看指定结点标签 # master结点默认标签 beta.kubernetes.io/arch=amd64 # cat > namespace-testxx.yaml <labels: labelnamexx: valuexxx EOF # kubectl apply -f namespace-testxx.yaml ★镜像获取方式imagePullPolicy

wordpress 5 labels: 6 app: wordpress 7 --- 8 apiVersion: v1 9 kind: PersistentVolumeClaim 10 metadata: 11 name: mysql-pv-claim 12 namespace: wordpress 13 labels: 14 app: wordpress kind: PersistentVolumeClaim 25 metadata: 26 name: wp-pv-claim 27 namespace: wordpress 28 labels: 29 app: wordpress 30 spec: 31 accessModes: 32 - ReadWriteOnce 33 resources: 34 apiVersion: v1 2 kind: Service 3 metadata: 4 name: wordpress-mysql 5 namespace: wordpress 6 labels: 7 app: wordpress 8 spec: 9 ports: 10 - port: 3306 11 selector: 12 app:

GitHub: @figo Steve Wong Hui Luo Presenter Bios 3 Abstract ​Kubernetes allows using topology labels to affect the scheduler’s placement of pods. This is used to spread pods across availability zones rules based on node labels, or based on placement of other pods constrain which nodes your pod is eligible to be scheduled on based on labels on the node • Some labels are automatically created Zones – label nodes with failure zone/regions Taints / Tolerations – mark nodes with arbitrary labels which could correspond to resource or whatever you like Admission Controller – a wide variety

@embano1 Steve Wong Michael Gasch Presenter Bios 3 Abstract Kubernetes allows using topology labels to affect the scheduler’s placement of pods. This is used to spread pods across availability zones rules based on node labels, or based on placement of other pods constrain which nodes your pod is eligible to be scheduled on based on labels on the node • Some labels are automatically created Zones – label nodes with failure zone/regions Taints / Tolerations – mark nodes with arbitrary labels which could correspond to resource or whatever you like Admission Controller – a wide variety

ReplicationController metadata: name: redis-master labels: name: redis-master spec: replicas: 1 selector: name: redis-master template: metadata: labels: name: redis-master 1-42 Kubernetes

kind: Deployment metadata: name: is spec: replicas: 3 template: metadata: labels: app: is spec: containers: - name: is image: registry/infra/is:6

of tree: the Kubernetes vSphere Cloud Provider Why it exists Handles identification of nodes Labels nodes with zone information (optional) Used to handle persistent volume provisioning, now done by

job-1574739729783- podgroup volcano.sh/task-spec: spark-driver createTimestamp: “2019-11-27T09:33:19Z” labels: spark-app-selector:spark- 6cc54577d7254b2d84924500375112f7 spark-role: driver name: job-1574739729783-driver