Heaven.Blog

KIND:     ReplicaSet

VERSION:  apps/v1

RESOURCE: selector <Object>

DESCRIPTION:

Selector is a label query over pods that should match the replica count.

Label keys and values that must match in order to be controlled by this

replica set. It must match the pod template’s labels. More info:

https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors

A label selector is a label query over a set of resources. The result of

matchLabels and matchExpressions are ANDed. An empty label selector matches

all objects. A null label selector matches no objects.

FIELDS:

matchExpressions     <[]Object>

matchExpressions is a list of label selector requirements. The requirements

are ANDed.

matchLabels  <map[string]string>

matchLabels is a map of {key,value} pairs. A single {key,value} in the

matchLabels map is equivalent to an element of matchExpressions, whose key

field is “key”, the operator is “In”, and the values array contains only

“value”. The requirements are ANDed.

matchExpressions is a list of label selector requirements. The requirements

are ANDed.

A label selector requirement is a selector that contains values, a key, and

an operator that relates the key and values.

FIELDS:

key  <string> -required-

key is the label key that the selector applies to.

operator     <string> -required-

operator represents a key’s relationship to a set of values. Valid

operators are In, NotIn, Exists and DoesNotExist.

values       <[]string>

values is an array of string values. If the operator is In or NotIn, the

values array must be non-empty. If the operator is Exists or DoesNotExist,

the values array must be empty. This array is replaced during a strategic

merge patch.

– key: pod-name

values:[aaa,bbb]

operator: DoesNotExist

kind: DaemonSet

metadata:

name: test-deamon

spec:

selector:

matchLabels:

name: deamon

template:

metadata:

labels:

name: deamon

spec:

containers:

– name: test-deamon-pod

image: nginx

podManagementPolicy  <string>

podManagementPolicy controls how pods are created during initial scale up,

when replacing pods on nodes, or when scaling down. The default policy is

`OrderedReady`, where pods are created in increasing order (pod-0, then

pod-1, etc) and the controller will wait until each pod is ready before

continuing. When scaling down, the pods are removed in the opposite order.

The alternative policy is `Parallel` which will create pods in parallel to

match the desired scale without waiting, and on scale down will delete all

pods at once.

replicas     <integer>

replicas is the desired number of replicas of the given Template. These are

replicas in the sense that they are instantiations of the same Template,

but individual replicas also have a consistent identity. If unspecified,

defaults to 1.

revisionHistoryLimit <integer>

revisionHistoryLimit is the maximum number of revisions that will be

maintained in the StatefulSet’s revision history. The revision history

consists of all revisions not represented by a currently applied

StatefulSetSpec version. The default value is 10.

selector     <Object> -required-

selector is a label query over pods that should match the replica count. It

must match the pod template’s labels. More info:

https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors

serviceName  <string> -required-

serviceName is the name of the service that governs this StatefulSet. This

service must exist before the StatefulSet, and is responsible for the

network identity of the set. Pods get DNS/hostnames that follow the

pattern: pod-specific-string.serviceName.default.svc.cluster.local where

“pod-specific-string” is managed by the StatefulSet controller.

template     <Object> -required-

template is the object that describes the pod that will be created if

insufficient replicas are detected. Each pod stamped out by the StatefulSet

will fulfill this Template, but have a unique identity from the rest of the

StatefulSet.

updateStrategy       <Object>

updateStrategy indicates the StatefulSetUpdateStrategy that will be

employed to update Pods in the StatefulSet when a revision is made to

Template.

volumeClaimTemplates <[]Object>

volumeClaimTemplates is a list of claims that pods are allowed to

reference. The StatefulSet controller is responsible for mapping network

identities to claims in a way that maintains the identity of a pod. Every

claim in this list must have at least one matching (by name) volumeMount in

one container in the template. A claim in this list takes precedence over

any volumes in the template, with the same name.

kind: StatefulSet  ### 有状态副本集

metadata:

name: sts-test

namespace: default

spec:

selector:

matchLabels:

app: sts-nginx

serviceName: “nginx”

replicas: 3 # 三个副本

template: ## Pod模板

metadata:

labels:

app: sts-nginx

spec:

containers:

– name: nginx

image: nginx

kind: Service

metadata:

name: nginx  ## 和上面的serviceName

namespace: default

spec:

selector:

app: sts-nginx

clusterIP: None  ## 不要分配ClusterIP,headless service，整个集群的Pod能直接访问

# 浏览器目前不能访问，如果需要浏览器访问,考虑使用Ingress

# NodePort 这样任意的机器都可以进行访问,只要能访问到集群的任意一个机器

type: ClusterIP

ports:

– name: http

port: 80

targetPort: 80

kind: Job

metadata:

name: job-test

spec:

template:

spec:

containers:

– name: pi

image: busybox  ## job类型的pod，不要用阻塞式的。如nginx。Deployment才应该是阻塞式的

command: [“/bin/sh”,”-c”,”ping -c 10 baidu.com”]

restartPolicy: Never #Job情况下，不支持Always

kind: Job

metadata:

name: job-test-04

spec:

completions: 5  ## 前一次必须结束才会下一次

parallelism: 3

template:

spec:

containers:

– name: pi

image: busybox  ## job类型的pod，不要用阻塞式的。如nginx。Deployment才应该是阻塞式的

command: [“/bin/sh”,”-c”,”ping -c 10 baidu.com”]

restartPolicy: Never #Job情况下，不支持Always

# backoffLimit: 4 #任务4次都没成，认为失败

activeDeadlineSeconds: 600    ## 整个Job的存活时间，超出就自动杀死

ttlSecondsAfterFinished: 10  ### 运行完成后自己删除

kind: CronJob

metadata:

name: hello

spec:

schedule: “*/1 * * * *”    #分、时、日、月、周

jobTemplate:

# kind: Job

spec:  ## 以下是Job的写法

template:

spec:

containers:

– name: hello

image: busybox

args:

– /bin/sh

– -c

– date; echo Hello from the Kubernetes cluster