"파드 kube-scheduler"의 두 판 사이의 차이

2024년 2월 21일 (수) 13:19 기준 최신판

1 개요[ | ]

pod/kube-scheduler
파드 kube-scheduler

$ kubectl get no
NAME           STATUS   ROLES           AGE   VERSION
controlplane   Ready    control-plane   16d   v1.29.0
node01         Ready    <none>          16d   v1.29.0

$ kubectl get pod -n kube-system -ojson | jq -r '.items | map(select(.metadata.ownerReferences[]?.kind == "Node" ) | .metadata.name) | .[]'
etcd-controlplane
kube-apiserver-controlplane
kube-controller-manager-controlplane
kube-scheduler-controlplane

$ kubectl get pod -n kube-system kube-scheduler-controlplane -oyaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubernetes.io/config.hash: b89e0a38d2f630290f39ad72d802321c
    kubernetes.io/config.mirror: b89e0a38d2f630290f39ad72d802321c
    kubernetes.io/config.seen: "2024-02-04T07:55:46.175903954Z"
    kubernetes.io/config.source: file
  creationTimestamp: "2024-02-04T07:56:09Z"
  labels:
    component: kube-scheduler
    tier: control-plane
  name: kube-scheduler-controlplane
  namespace: kube-system
  ownerReferences:
  - apiVersion: v1
    controller: true
    kind: Node
    name: controlplane
    uid: 3dc60cbe-4e9b-4852-af95-22542229bf7d
  resourceVersion: "2099"
  uid: e75c57c4-ca7b-44ef-b9a3-204cc7d6db53
spec:
  containers:
  - command:
    - kube-scheduler
    - --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
    - --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
    - --bind-address=127.0.0.1
    - --kubeconfig=/etc/kubernetes/scheduler.conf
    - --leader-elect=true
    image: registry.k8s.io/kube-scheduler:v1.29.0
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10259
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 15
    name: kube-scheduler
    resources:
      requests:
        cpu: 25m
    startupProbe:
      failureThreshold: 24
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10259
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 15
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/kubernetes/scheduler.conf
      name: kubeconfig
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  hostNetwork: true
  nodeName: controlplane
  preemptionPolicy: PreemptLowerPriority
  priority: 2000001000
  priorityClassName: system-node-critical
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext:
    seccompProfile:
      type: RuntimeDefault
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    operator: Exists
  volumes:
  - hostPath:
      path: /etc/kubernetes/scheduler.conf
      type: FileOrCreate
    name: kubeconfig
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2024-02-21T02:44:49Z"
    status: "True"
    type: PodReadyToStartContainers
  - lastProbeTime: null
    lastTransitionTime: "2024-02-21T02:44:47Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2024-02-21T02:45:04Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2024-02-21T02:45:04Z"
    status: "True"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2024-02-21T02:44:47Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: containerd://1ebd642c9abd44c186d7c49d39da75f721e8aedb441d64e73287c016635d9d0a
    image: registry.k8s.io/kube-scheduler:v1.29.0
    imageID: registry.k8s.io/kube-scheduler@sha256:5df310234e4f9463b15d166778d697830a51c0037ff28a1759daaad2d3cde991
    lastState:
      terminated:
        containerID: containerd://f7d5a0f4242ce52ec808ec3a7ed9064ec0599857524278844f4e893a232cd0e6
        exitCode: 255
        finishedAt: "2024-02-21T02:44:35Z"
        reason: Unknown
        startedAt: "2024-02-04T08:11:05Z"
    name: kube-scheduler
    ready: true
    restartCount: 2
    started: true
    state:
      running:
        startedAt: "2024-02-21T02:44:48Z"
  hostIP: 172.30.1.2
  hostIPs:
  - ip: 172.30.1.2
  phase: Running
  podIP: 172.30.1.2
  podIPs:
  - ip: 172.30.1.2
  qosClass: Burstable
  startTime: "2024-02-21T02:44:47Z"

2 같이 보기[ | ]

@@ 161번째 줄: / 161번째 줄: @@
 [[분류: k8s]]
+[[분류: kube-system]]
+[[분류: killercoda]]