본문 바로가기

IT 엔지니어/CLOUD

DOCKER NAMESPACE/STATEFULSET

[디폴트 네임스페이스 변경]

[기존 네임스페이스 확인]
kubectl config view

[context 생성 및 추가]
kubectl config set-context kubernetes-user@cluster.local --cluster=cluster.local --user=kubernetes-admin --namespace=myns1

Context "kubernetes-user@cluster.local" created.

 

추가 CONTEXT

 

 

[기존 context 확인]

$ kubectl config current-context 
<kubernetes-admin@cluster.local>

[kubernetes-user@cluster.local로 변경]

$ kubectl config use-context kubernetes-user@cluster.local

Switched to context "kubernetes-user@cluster.local".

[변경사항 확인]

$ kubectl config current-context 
<kubernetes-user@cluster.local>
---------------------------------------
[네임스페이스 생성]
kubectl create namespace myns1

[파드 생성]
kubectl run myweb --image nginx --port 80

[디폴트 변경 확인]
kubectl get pods

kubectl get pods -n default

 

 

 

 

 

[원상복구]

[kubernetes-admin@cluster.local로 변경]
TAB

$ kubectl config use-context kubernetes-admin@cluster.local

Switched to context "kubernetes-admin@cluster.local".

kubectl get ns(=namespace)

kubectl get lease -n kube-node-lease

 

 

 

 

 

[Deployment 파드 이름 순차 생성]

kubectl get deploy web -o yaml > test.yml

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: "2025-04-16T08:28:06Z"
  generation: 2
  labels:
    app: web
  name: web
  namespace: default
  resourceVersion: "98678"
  uid: 0b7c58d1-7450-4073-a817-b8244015fb69
spec:
  progressDeadlineSeconds: 600
  replicas: 3
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: web
  ~~strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate~~
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: web
    spec:
      containers:
      - image: nginx
        imagePullPolicy: Always
        name: nginx
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
status:
  availableReplicas: 3
  conditions:
  - lastTransitionTime: "2025-04-16T08:28:06Z"
    ~~lastUpdateTime: "2025-04-16T08:28:10Z"~~
    message: ReplicaSet "web-844f65fb5" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: "2025-04-16T08:29:22Z"
    ~~lastUpdateTime: "2025-04-16T08:29:22Z"~~
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 2
  readyReplicas: 3
  replicas: 3
  updatedReplicas: 3

vi test.yml 수정

apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: "2025-04-16T08:28:06Z"
  generation: 2
  labels:
    app: web
  name: web
  namespace: default
  resourceVersion: "98678"
  uid: 0b7c58d1-7450-4073-a817-b8244015fb69
spec:
  ***serviceName: "test"***
  replicas: 3
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: web
  template:
    metadata:
      labels:
        app: web
    spec:
      containers:
      - image: nginx
        imagePullPolicy: Always
        name: nginx
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
status:
  availableReplicas: 3
  conditions:
  - lastTransitionTime: "2025-04-16T08:28:06Z"
    message: ReplicaSet "web-844f65fb5" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: "2025-04-16T08:29:22Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 2
  readyReplicas: 3
  replicas: 3
  updatedReplicas: 3

 

 

 

 

해당 YAML 파일 작성으로 기존 해시값으로 생성된 이름에서

단순한 정수 순서대로 파일 생성됨 확인

'IT 엔지니어 > CLOUD' 카테고리의 다른 글

K8S 실습  (1) 2025.05.23
K8S POD 생성  (0) 2025.05.22
Docker POD  (1) 2025.05.21
Docker 기본 명령어  (0) 2025.05.20
Docker Kubespray -1  (0) 2025.05.19