$ brew install kind

$ kind version
kind v0.23.0 go1.22.3 darwin/amd64

$ kind create cluster --image=kindest/node:v1.29.0
Thanks for using kind! 😊

$ kind get clusters
kind
$ kind delete cluster -n kind

$ kubectl cluster-info --context kind-kind
Kubernetes control plane is running at https://127.0.0.1:53902
CoreDNS is running at https://127.0.0.1:53902/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

$ cat ~/.kube/config
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: 省略
    server: https://127.0.0.1:53902
  name: kind-kind
contexts: //クラスタの設定情報ごとに名前のついたコンテキストが作成される
- context:
    cluster: kind-kind
    user: kind-kind
  name: kind-kind
current-context: kind-kind
kind: Config
preferences: {}
users:
- name: kind-kind
  user:
    client-certificate-data: 省略
    client-key-data: 省略

$ kind delete cluster
Deleting cluster "kind" ...
Deleted nodes: ["kind-control-plane"]

$ kubectl get pod --namespace kube-system
NAME                                         READY   STATUS    RESTARTS   AGE
etcd-kind-control-plane                      1/1     Running   0          13s
kube-apiserver-kind-control-plane            1/1     Running   0          13s
kube-controller-manager-kind-control-plane   1/1     Running   0          13s
kube-scheduler-kind-control-plane            1/1     Running   0          13s

$ kubectl get nodes
NAME                 STATUS   ROLES           AGE   VERSION
kind-control-plane   Ready    control-plane   21m   v1.29.0

$ kind get clusters
kind // デフォルトで作成されるクラスタ名はkind

$ kubectl get pod --namespace default
No resources found in default namespace.

$ kubectl get pod myapp --namespace default
NAME    READY   STATUS    RESTARTS   AGE
myapp   1/1     Running   0          5d23h

kubectl get pod myapp -o yaml -n default | less

kubectl get pod myapp -o yaml -n default > pod.yml

$ kubectl get pod myapp --output jsonpath='{.spec.containers[].image}'
blux2/hello-server:1.0

$ kubectl get pod myapp --output json --namespace default | jq '.spec.containers[].image'
"blux2/hello-server:1.0"

kubectl describe pod myapp

kubectl logs <Pod名>

$ kubectl logs myapp -c hello-server -n default
2024/08/15 15:02:39 Starting server on port 8080

kubectl get pod <Pod名> --v=<ログレベル>

$ kubectl apply --filename kind/myapp.yml --namespace default
pod/myapp created
$ kubectl get pod --namespace default
NAME    READY   STATUS    RESTARTS   AGE
myapp   1/1     Running   0          47s

$ kubectl run myapp2 --image=blux2/hello-server:1.0 --namespace default
pod/myapp2 created

$ kubectl get pod --namespace default
NAME     READY   STATUS    RESTARTS   AGE
myapp    1/1     Running   0          55m
myapp2   1/1     Running   0          46m

kubectl debug --stdin --tty <デバッグ対象Pod名> --image=<デバッグ用のコンテナのイメージ> --target=<デバッグ対象のコンテナ名>

$ kubectl debug --stdin --tty myapp --image=curlimages/curl:8.4.0 --target=hello-server --namespace default -- sh
Targeting container "hello-server". If you don't see processes from this container it may be because the container runtime doesn't support this feature.
Defaulting debug container name to debugger-zk4b7.
If you don't see a command prompt, try pressing enter.

~ $ curl localhost:8080
Hello, world!~ $
~ $

kubectl --namespace default run busybox --image=busybox:1.36.1 --rm --stdin --tty --restart=Never --command -- nslookup google.com
Server:		10.96.0.10
Address:	10.96.0.10:53

Non-authoritative answer:
Name:	google.com
Address: 142.251.42.142

Non-authoritative answer:
Name:	google.com
Address: 2404:6800:4004:825::200e

pod "busybox" deleted

kubectl exec --stdin --tty <Pod名> -- <コマンド名>

$ kubectl --namespace default run curlpod --image=curlimages/curl:8.4.0 --command -- /bin/sh -c "while true; do sleep infinity;done;"
pod/curlpod created

$ kubectl get pod -n default
NAME      READY   STATUS    RESTARTS   AGE
curlpod   1/1     Running   0          5m45s
myapp     1/1     Running   0          16d

myappコンテナのIPアドレスを取得
$ kubectl get pod myapp -o wide -n default
NAME    READY   STATUS    RESTARTS   AGE   IP           NODE                 NOMINATED NODE   READINESS GATES
myapp   1/1     Running   0          16d   10.244.0.5   kind-control-plane   <none>           <none>

curlpodに接続し、取得したIPにcurlを実行
$ kubectl -n default exec -it curlpod -- /bin/sh
~ $ curl 10.244.0.5:8080
Hello, world!

kubectl port-forward <Pod名> <転送先ポート番号>:<転送元ポート番号>

$ kubectl port-forward myapp 5555:8080 -n default
Forwarding from 127.0.0.1:5555 -> 8080
Forwarding from [::1]:5555 -> 8080

他のターミナルから実施
$ curl localhost:5555
Hello, world!

$ kubectl port-forward myapp 5555:8080 -n default
Forwarding from 127.0.0.1:5555 -> 8080
Forwarding from [::1]:5555 -> 8080
Handling connection for 5555

kubectl edit

$ kubectl edit pod myapp -n default
Edit cancelled, no changes made.

kubectl delete <リソース名>

$ kubectl get pod -n default
NAME      READY   STATUS    RESTARTS   AGE
curlpod   1/1     Running   0          7d4h
myapp     1/1     Running   0          23d
myapp2    1/1     Running   0          23d
myapp3    1/1     Running   0          8d
$ kubectl delete pod myapp -n default
pod "myapp" deleted
$ kubectl get pod -n default
NAME      READY   STATUS    RESTARTS   AGE
curlpod   1/1     Running   0          7d4h
myapp2    1/1     Running   0          23d
myapp3    1/1     Running   0          8d

kubectl get pods
kubectl get pod
kubectl get po

kubectl api-resources

Ingress
↑
Service
↑
Deployment
↑
ReplicaSet
↑
Pod(コンテナ)

$ k get po
NAME    READY   STATUS         RESTARTS   AGE
myapp   0/1     ErrImagePull   0          4m12s
↓
$ k get po
NAME    READY   STATUS             RESTARTS   AGE
myapp   0/1     ImagePullBackOff   0          39m

$ k describe pod myapp -n default
      Reason:       ImagePullBackOff
      ...
Events:
  Type     Reason     Age                 From               Message
  ----     ------     ----                ----               -------
  Normal   Scheduled  41m                 default-scheduler  Successfully assigned default/myapp to kind-control-plane
  Normal   Pulled     41m                 kubelet            Container image "blux2/hello-server:1.0" already present on machine
  Normal   Created    41m                 kubelet            Created container hello-server
  Normal   Started    41m                 kubelet            Started container hello-server
  Normal   Killing    37m                 kubelet            Container hello-server definition changed, will be restarted
  Warning  Failed     36m (x2 over 37m)   kubelet            Error: ImagePullBackOff
  Warning  Failed     35m (x4 over 37m)   kubelet            Failed to pull image "blux2/hello-server:1.1": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/blux2/hello-server:1.1": failed to resolve reference "docker.io/blux2/hello-server:1.1": docker.io/blux2/hello-server:1.1: not found
  Warning  Failed     35m (x4 over 37m)   kubelet            Error: ErrImagePull
  Warning  BackOff    34m (x6 over 36m)   kubelet            Back-off restarting failed container hello-server in pod myapp_default(dda6ffcc-f9ae-46d3-ac86-631df5aae09f)
  Normal   Pulling    26m (x7 over 37m)   kubelet            Pulling image "blux2/hello-server:1.1"
  Normal   BackOff    97s (x72 over 37m)  kubelet            Back-off pulling image "blux2/hello-server:1.1"

docker.io/blux2/hello-server:1.1: not found

$ kubectl edit pod myapp -n default
spec:
  containers:
  - image: blux2/hello-server:1.1
  ↓
  - image: blux2/hello-server:1.0

$ k get po -n default
NAME    READY   STATUS    RESTARTS       AGE
myapp   1/1     Running   1 (141m ago)   145m

ReplicaSet -> Pod
           -> Pod

Deployment -> ReplicaSet -> Pod
                         -> Pod
           -> ReplicaSet -> Pod
                         -> Pod

$ k apply -f replicaset.yaml -n default
replicaset.apps/httpserver created
$ k get pod -n default
NAME               READY   STATUS              RESTARTS   AGE
httpserver-7w7mh   0/1     ContainerCreating   0          12s
httpserver-fsgv7   0/1     ContainerCreating   0          12s
httpserver-xrvw5   0/1     ContainerCreating   0          12s

$ k get replicaset -n default
NAME         DESIRED   CURRENT   READY   AGE
httpserver   3         3         3       5m26s

$ k delete replicaset httpserver -n default
replicaset.apps "httpserver" deleted
$ k get replicaset -n default
No resources found in default namespace.

ReplicaSet -> Pod
           -> Pod

Deployment -> ReplicaSet -> Pod(v1)
                         -> Pod(v1)
           -> ReplicaSet -> Pod(v2)
                         -> Pod(v2)

$ kubectl apply -f deployment.yaml -n default
deployment.apps/nginx-deployment created

デプロイメントが作成される
$ kubectl get deployment -n default
NAME               READY   UP-TO-DATE   AVAILABLE   AGE
nginx-deployment   3/3     3            3           2m54s

レプリカセットも一つ作成される
$ kubectl get replicaset -n default
NAME                          DESIRED   CURRENT   READY   AGE
nginx-deployment-595dff4799   3         3         3       3m30s

ポッドはレプリカセットに紐づいている
$ kubectl get pods -n default
NAME                                READY   STATUS              RESTARTS   AGE
nginx-deployment-595dff4799-bxmgh   1/1     Running             0          18s
nginx-deployment-595dff4799-m4qcz   0/1     ContainerCreating   0          18s
nginx-deployment-595dff4799-q9kvv   0/1     ContainerCreating   0          18s

$ kubectl apply --filename deployment.yaml --namespace default
deployment.apps/nginx-deployment configured

Pod名が新しいものに置き換わっている
$ kubectl get pod --namespace default
NAME                                READY   STATUS    RESTARTS   AGE
nginx-deployment-789bf7b8fc-4lpb6   1/1     Running   0          111s
nginx-deployment-789bf7b8fc-fhmrf   1/1     Running   0          109s
nginx-deployment-789bf7b8fc-zwblr   1/1     Running   0          108s

ReplicaSetが新しくなっている
$ kubectl get replicaset --namespace default
NAME                          DESIRED   CURRENT   READY   AGE
nginx-deployment-595dff4799   0         0         0       6d2h
nginx-deployment-789bf7b8fc   3         3         3       3m12s

Deploymentは変わっていない
$ kubectl get deployment --namespace default
NAME               READY   UP-TO-DATE   AVAILABLE   AGE
nginx-deployment   3/3     3            3           6d2h

imageが指定したものに置き換わっている
$ kubectl get deployment nginx-deployment -o=jsonpath='{.spec.template.spec.containers[0].image}'
nginx:1.25.3

※jqで出力の場合
$ kubectl get deployment nginx-deployment -o json | jq .spec.template.spec.containers[0].image
"nginx:1.25.3"

RollingUpdateStrategy:  25% max unavailable, 25% max surge

Podが入れ替わったらアクセス先のIPを変える必要がある?
アプリケーション
  =>    Pod1  10.x.x.1
  =>    Pod2  10.x.x.2

Podが入れ替わってもIPが変わらないように構築する
アプリケーション
  =>  Service 10.x.x.5
    =>  Pod1  service.name.default.svc.cluster.local
    =>  Pod2  service.name.default.svc.cluster.local

$ kubectl apply -f deployment-hello-server.yaml -n default
deployment.apps/hello-server created

$ kubectl get pod -n default
NAME                            READY   STATUS    RESTARTS   AGE
hello-server-6cc6b44795-2csg5   1/1     Running   0          4s
hello-server-6cc6b44795-lsrsr   1/1     Running   0          4s
hello-server-6cc6b44795-z2llv   1/1     Running   0          4s

$ kubectl apply -f service.yaml -n default
service/hello-server-service created

$ kubectl get service -n default
NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
hello-server-service   ClusterIP   10.96.141.145   <none>        8080/TCP   29s
kubernetes             ClusterIP   10.96.0.1       <none>        443/TCP    78d

作成したServiceに対してポートフォワードを設定
$ kubectl port-forward svc/hello-server-service 8080:8080 -n default
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080

接続できること
$ curl localhost:8080
Hello, world!

ClusterIPを確認する
$ kubectl get service hello-server-service -n default
NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
hello-server-service   ClusterIP   10.96.141.145   <none>        8080/TCP   29m

一時的なコンテナを立ち上げ、ClusterIPにcurlを実行する
$ kubectl run curl --image curlimages/curl --rm --stdin --tty --restart=Never --command -- curl 10.96.141.145:8080
Hello, world!pod "curl" deleted

$ kubectl apply -f service-nodeport.yaml -n default
service/hello-server-external created

$ kubectl apply -f deployment-hello-server.yaml -n default
deployment.apps/hello-server created

$ kubectl get deployments hello-server
NAME           READY   UP-TO-DATE   AVAILABLE   AGE
hello-server   3/3     3            3           33s

$ kubectl get service hello-server-external
NAME                    TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
hello-server-external   NodePort   10.96.142.76   <none>        8080:30599/TCP   3m10s

※10.96.142.76はあくまでCLUSTER-IP

$ kubectl get nodes -o json | jq .'items[]'.status.addresses
[
  {
    "address": "172.18.0.2",
    "type": "InternalIP"
  },
  {
    "address": "kind-nodeport-control-plane",
    "type": "Hostname"
  }
]

$ curl localhost:30599
Hello, world!

※本来↑で取得したIPでアクセスできるはずだが、kind + Docker Desktop環境のためlocalhostでアクセス

$ kubectl get service hello-server-service -n default
NAME                   TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
hello-server-service   ClusterIP   10.96.185.55   <none>        8080/TCP   60s


$ kubectl get deployments.apps hello-server -n default
NAME           READY   UP-TO-DATE   AVAILABLE   AGE
hello-server   3/3     3            3           27m

ClusterIPでcurl実行
$ kubectl -n default run curl --image curlimages/curl --rm --stdin --tty --restart=Never --command -- curl 10.96.185.55:8080
Hello, world!pod "curl" deleted

FQDNでアクセス
$ kubectl -n default run curl --image curlimages/curl --rm --stdin --tty --restart=Never --command -- curl hello-server-service.default.svc.cluster.local:8080
Hello, world!pod "curl" deleted

apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-server
  labels:
    app: hello-server
spec:
  replicas: 3
  selector:
    matchLabels:
      app: hello-server
  template:
    metadata:
      labels:
        app: hello-server
    spec:
      containers:
      - name: hello-server
        image: blux2/hello-server:1.0
        ports:
        - containerPort: 8080

$ kubectl apply -f service-nodeport.yaml -n default

$ kubectl get service hello-server-external -o json | jq ".spec.ports[0].nodePort"
30599

$ kubectl apply -f hello-server.yaml -n default

$ kubectl get deployments -n default
NAME           READY   UP-TO-DATE   AVAILABLE   AGE
hello-server   3/3     3            3           5d23h

$ kubectl get pods -n default
NAME                            READY   STATUS    RESTARTS   AGE
hello-server-6cc6b44795-6pltq   1/1     Running   0          5d23h
hello-server-6cc6b44795-6vvkw   1/1     Running   0          5d23h
hello-server-6cc6b44795-t26ms   1/1     Running   0          5d23h

$ kubectl get nodes -n default -o json | jq '.items[0].status.addresses[0]'
{
  "address": "172.18.0.2",
  "type": "InternalIP"
}

$ curl localhost:30599 # Docker + kind環境のためlocalhostでアクセス
Hello, world!

間違った定義を持つserviceのyamlを読み込ませる
$ kubectl apply -f service-destruction.yaml -n default
service/hello-server-external configured

curlが失敗するようになる
$ curl localhost:30599
curl: (52) Empty reply from server

Podの確認
$ kubectl get pod -n default
NAME                            READY   STATUS    RESTARTS   AGE
hello-server-6cc6b44795-6pltq   1/1     Running   0          5d23h
hello-server-6cc6b44795-6vvkw   1/1     Running   0          5d23h
hello-server-6cc6b44795-t26ms   1/1     Running   0          5d23h

Podは問題なく動作している

Deploymentの確認
$ kubectl get deployment -n default
NAME           READY   UP-TO-DATE   AVAILABLE   AGE
hello-server   3/3     3            3           5d23h

Deploymentも正常に動いている


Serviceリソースを確認する
$ kubectl get service -n default
NAME                    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
hello-server-external   NodePort    10.96.253.93   <none>        8080:30599/TCP   26m
kubernetes              ClusterIP   10.96.0.1      <none>        443/TCP          5d23h

こちらも問題ない

Pod名を確認する
$ kubectl get pod -n default
NAME                            READY   STATUS    RESTARTS   AGE
hello-server-6cc6b44795-6pltq   1/1     Running   0          5d23h
hello-server-6cc6b44795-6vvkw   1/1     Running   0          5d23h
hello-server-6cc6b44795-t26ms   1/1     Running   0          5d23h

デバッグ用コンテナを作成してlocalhostににアクセスする
$ kubectl -n default debug --stdin --tty hello-server-6cc6b44795-6pltq --image curlimages/curl --target=hello-server -- sh
Targeting container "hello-server". If you don't see processes from this container it may be because the container runtime doesn't support this feature.
Defaulting debug container name to debugger-hx754.
If you don't see a command prompt, try pressing enter.
~ $
~ $ curl localhost:8080
Hello, world!
~ $ exit
Session ended, the ephemeral container will not be restarted but may be reattached using 'kubectl attach hello-server-6cc6b44795-6pltq -c debugger-hx754 -i -t' if it is still running

Podの一覧からIPを確認する
$ kubectl get pods -o custom-columns=NAME:.metadata.name,IP:.status.podIP
NAME                            IP
hello-server-6cc6b44795-6pltq   10.244.0.7
hello-server-6cc6b44795-6vvkw   10.244.0.5
hello-server-6cc6b44795-t26ms   10.244.0.6

新規作成Podから確認を行う
$ kubectl -n default run curl --image curlimages/curl --rm --stdin --tty --restart=Never --command -- curl 10.244.0.7:8080
Hello, world!pod "curl" deleted

Serviceの情報を取得する
$ kubectl get svc -o custom-columns=NAME:.metadata.name,IP:.spec.clusterIP
NAME                    IP
hello-server-external   10.96.253.93
kubernetes              10.96.0.1

ServiceのIPアドレスを利用し、Service経由でアプリケーションにアクセスする
$ kubectl -n default run curl --image curlimages/curl --rm --stdin --tty --restart=Never --command -- curl 10.96.253.93:8080
curl: (7) Failed to connect to 10.96.253.93 port 8080 after 0 ms: Could not connect to server
pod "curl" deleted
pod default/curl terminated (Error)

Serviceの内容を確認する
$ kubectl describe service hello-server-external -n default
Name:                     hello-server-external
Namespace:                default
Labels:                   <none>
Annotations:              <none>
Selector:                 app=hello-serve
Type:                     NodePort
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       10.96.253.93
IPs:                      10.96.253.93
Port:                     <unset>  8080/TCP
TargetPort:               8080/TCP
NodePort:                 <unset>  30599/TCP
Endpoints:                <none>
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

正  hello-server
誤  hello-serve

$ kubectl diff -f service.yaml -n default
diff -u -N /var/folders/bb/d1sylzs13hl9263mst4kc87w0000gn/T/LIVE-2328208767/v1.Service.default.hello-server-external /var/folders/bb/d1sylzs13hl9263mst4kc87w0000gn/T/MERGED-1134889556/v1.Service.default.hello-server-external
--- /var/folders/bb/d1sylzs13hl9263mst4kc87w0000gn/T/LIVE-2328208767/v1.Service.default.hello-server-external	2024-11-08 17:03:44
+++ /var/folders/bb/d1sylzs13hl9263mst4kc87w0000gn/T/MERGED-1134889556/v1.Service.default.hello-server-external	2024-11-08 17:03:44
@@ -24,7 +24,7 @@
     protocol: TCP
     targetPort: 8080
   selector:
-    app: hello-serve
+    app: hello-server
   sessionAffinity: None
   type: NodePort
 status:

$ kubectl apply -f hello-server-env.yaml -n default
deployment.apps/hello-server created
configmap/hello-server-configmap created

deploymentとconfigmapの確認
$ kubectl get deployment,configmap -n default
NAME                           READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/hello-server   1/1     1            1           64s

NAME                               DATA   AGE
configmap/hello-server-configmap   1      63s
configmap/kube-root-ca.crt         1      23m

hello-server-configmapに設定された値の確認
$ kubectl get configmap hello-server-configmap -o json | jq .data
{
  "PORT": "8081"
}

$ kubectl port-forward deployments/hello-server 8081:8081 -n default
Forwarding from 127.0.0.1:8081 -> 8081
Forwarding from [::1]:8081 -> 8081
Handling connection for 8081

$ curl localhost:8081
Hello, world! Let's learn Kubernetes!

$ kubectl apply -f new-config-map.yaml
deployment.apps/hello-server unchanged
configmap/hello-server-configmap configured

ConfigMap経由で設定した環境変数はアプリケーションの再起動が必要
$ kubectl rollout restart deployment/hello-server -n default
deployment.apps/hello-server restarted

$ kubectl port-forward deployments/hello-server 8082:8082 -n default
Forwarding from 127.0.0.1:8082 -> 8082
Forwarding from [::1]:8082 -> 8082
Handling connection for 8082

$ curl localhost:8082
Hello, world! Let's learn Kubernetes!

% kubectl apply -f hello-server-volume.yaml -n default
deployment.apps/hello-server configured
configmap/hello-server-configmap created
%
% kubectl get pod -n default
NAME                            READY   STATUS    RESTARTS   AGE
hello-server-56f54cc4fc-5nvqf   1/1     Running   0          15s
hello-server-56f54cc4fc-dq9pc   1/1     Running   0          8s
hello-server-56f54cc4fc-vf4ss   1/1     Running   0          9s
% kubectl port-forward deployments/hello-server 8080:8080
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
Handling connection for 8080

% curl localhost:8080
I am hungry.

apiVersion: batch/v1
kind: Job
metadata:
  name: date-checker
spec:
  template:
    spec:
      containers:
      - name: date
        image: ubuntu:22.04  // Jobで起動するコンテナに利用するイメージを指定
        command: ["date"]  // コンテナ内で実行するコマンドを指定
      restartPolicy: Never
  backoffLimit: 4

% kubectl apply -f job.yaml -n default
job.batch/date-checker created
% kubectl get pod -n default
NAME                 READY   STATUS              RESTARTS   AGE
date-checker-6sgwx   0/1     ContainerCreating   0          4s

% kubectl describe job date-checker -n default
Name:             date-checker
Namespace:        default
Selector:         batch.kubernetes.io/controller-uid=c6afa4cf-9cf0-4c1c-9c3c-9e8010ee7c1e
Labels:           batch.kubernetes.io/controller-uid=c6afa4cf-9cf0-4c1c-9c3c-9e8010ee7c1e
                  batch.kubernetes.io/job-name=date-checker
                  controller-uid=c6afa4cf-9cf0-4c1c-9c3c-9e8010ee7c1e
                  job-name=date-checker
Annotations:      <none>
Parallelism:      1
Completions:      1
Completion Mode:  NonIndexed
Suspend:          false
Backoff Limit:    4
Start Time:       Fri, 03 Jan 2025 21:23:34 +0900
Completed At:     Fri, 03 Jan 2025 21:23:44 +0900
Duration:         10s
Pods Statuses:    0 Active (0 Ready) / 1 Succeeded / 0 Failed
Pod Template:
  Labels:  batch.kubernetes.io/controller-uid=c6afa4cf-9cf0-4c1c-9c3c-9e8010ee7c1e
           batch.kubernetes.io/job-name=date-checker
           controller-uid=c6afa4cf-9cf0-4c1c-9c3c-9e8010ee7c1e
           job-name=date-checker
  Containers:
   date:
    Image:      ubuntu:22.04
    Port:       <none>
    Host Port:  <none>
    Command:
      date
    Environment:   <none>
    Mounts:        <none>
  Volumes:         <none>
  Node-Selectors:  <none>
  Tolerations:     <none>
Events:
  Type    Reason            Age   From            Message
  ----    ------            ----  ----            -------
  Normal  SuccessfulCreate  85s   job-controller  Created pod: date-checker-6sgwx
  Normal  Completed         75s   job-controller  Job completed

apiVersion: batch/v1
kind: CronJob
metadata:
  name: date
spec:
  schedule: "*/2 * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: date
            image: ubuntu:22.04
            command: ["date"]
          restartPolicy: Never

% kubectl get cronjob -n default
NAME   SCHEDULE      SUSPEND   ACTIVE   LAST SCHEDULE   AGE
date   */2 * * * *   False     0        <none>          40s
% kubectl get job -n default
NAME            COMPLETIONS   DURATION   AGE
date-28931818   1/1           3s         2m50s
date-28931820   1/1           3s         50s

apiVersion: v1
kind: Pod
metadata:
  labels:
    app: httpserver
  name: httpserver-readiness
spec:
  containers:
  - name: httpserver
    image: blux2/delayfailserver:1.1
    readinessProbe: # 200~400で成功、失敗時はPodをServiceから外す
      httpGet:
        path: /healthz # エンドポイントを指定
        port: 8080 # エンドポイントのポートを指定
      initialDelaySeconds: 5
      periodSeconds: 5
    livenessProbe: # 200~400で成功、失敗時はPodを再起動する
      httpGet:
        path: /healthz
        port: 8080
      initialDelaySeconds: 5
      periodSeconds: 5

spec:
  containers:
  - name: hello-server
    image: blux2/hello-server:1.6
    resources:
      requests:
        memory: "64Mi"
        cpu: "10m"
      limits:
        memory: "64Mi"
        cpu: "10m"

kind: Pod
apiVersion: v1
metadata:
  name: mypod
  labels:
    app: nginx
spec:
  topologySpreadConstraints:
  - maxSkew: 1 # Node間でのコンテナ数の最大差分数を定義
    topologyKey: zone
    whenUnsatisfiable: DoNotSchedule
    labelSelector:
      matchLabels:
        app: nginx
  containers:
  - name: nginx
    image: nginx:1.25.3

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: hello-server-hpa
spec:
  minReplicas: 1    # Podの最小数を指定
  maxReplicas: 10   # Podの最大数を指定
  metrics:
  - resource:
      name: cpu
      target:
        averageUtilization: 50 # 全体のCPU使用率が50%を下回るようにPodを増減する
        type: Utilization
    type: Resource
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: hpa-handson

apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-server
  labels:
    app: hello-server
spec:
  replicas: 3
  selector:
    matchLabels:
      app: hello-server
  template:
    metadata:
      labels:
        app: hello-server
    spec:
      containers:
      - name: hello-server
        image: blux2/hello-server:1.8

apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: hello-server-pdb
spec:
  minAvailable: 2
  selector:
    matchLabels:
      app: hello-server