➜  kubernetes kind create cluster --image=kindest/node:v1.29.8
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.29.8) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹️
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂

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

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

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

apiVersion: v1
kind: Pod // kimd はpod
metadata:
  name: nginx // podの名前をnginx
spec: // コンテナの仕様 dockerfileなくても作成できるみたい
  containers:
  - name: nginx
    image: nginx:1.25.3
    ports:
    - containerPort: 80

apiVersion: v1
kind: Pod
metadata:
  name: myapp
  labels:
    app: myapp
spec:
  containers:
  - name: hello-server
    image: blux2/hello-server:1.0
    ports:
    - containerPort: 8080

// クラスターがないとだめ
kind create cluster --image=kindest/node:v1.29.8

➜  kubernetes  kubectl get nodes
NAME                 STATUS     ROLES           AGE   VERSION
kind-control-plane   NotReady   control-plane   10s   v1.29.8

➜  kubernetes kind get clusters
kind

// podがあるか
➜  kubernetes kubectl get pod --namespace default
No resources found in default namespace.

➜  kubernetes kubectl apply --filename myapp.yaml --namespace default
pod/myapp created

// 2つ目のpodを作成してる
➜  kubernetes kubectl run myapp2 --image=blux2/hello-server:1.0 --namespace default
pod/myapp created

// 作成された
➜  kubernetes kubectl get pod --namespace default
NAME    READY   STATUS    RESTARTS   AGE
myapp   1/1     Running   0          11s

// output

kubectl get pod --output yaml  --namespace default
kubectl get pod --output wide  --namespace default

// wideつけるとnodeの情報まで
➜  kubernetes kubectl get pod --output wide  --namespace default
NAME    READY   STATUS    RESTARTS   AGE   IP           NODE                 NOMINATED NODE   READINESS GATES
myapp   1/1     Running   0          14m   10.244.0.5   kind-control-plane   <none>           <none>
➜  kubernetes kubectl get pod --namespace default
NAME    READY   STATUS    RESTARTS   AGE
myapp   1/1     Running   0          14m
➜  kubernetes

// podのステータスを確認できる
➜  kubernetes kubectl get pod --namespace default
NAME    READY   STATUS    RESTARTS   AGE
myapp   1/1     Running   0          3m55s

// これでdiffをとったりするみたい
kubectl get pod --output yaml  --namespace default > pod.yaml

// json はjqみたいなことができる

kubectl get pod --output jsonpath='{.spec.containers[].image}'  --namespace default

## describe
➜  kubernetes kubectl describe pod myapp
Name:             myapp
Namespace:        default
Priority:         0
Service Account:  default
Node:             kind-control-plane/172.18.0.2
Start Time:       Sat, 26 Jul 2025 12:19:08 +0900
Labels:           app=myapp
Annotations:      <none>
Status:           Running
IP:               10.244.0.5
IPs:
  IP:  10.244.0.5
Containers:
  hello-server:
    Container ID:   containerd://6fd23a5ecff1a94706fa5df03862d0295b57089e557281e7f5ee40ecde23297e
    Image:          blux2/hello-server:1.0
    Image ID:       docker.io/blux2/hello-server@sha256:35ab584cbe96a15ad1fb6212824b3220935d6ac9d25b3703ba259973fac5697d
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Sat, 26 Jul 2025 12:19:13 +0900
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-n44ml (ro)


## logs

// podのログが見れる
➜  kubernetes kubectl logs myapp
2025/07/26 03:19:13 Starting server on port 8080

apiVersion: v1
kind: Pod
metadata:
  name: myapp
  labels:
    app: myapp
spec:
  containers:
  - name: hello-server
    image: blux2/hello-server:1.0
    ports:
    - containerPort: 8080

## デバック用のコンテナを立てて、curlする
// --targetはcurl先のコンテナを明示してる

kubectl debug --stdin --tty myapp --image=curlimages/curl:8.4.0 --target=hello-server --namespace default -- sh

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

// curl のpodもできた
➜  kubernetes k get pod --output wide
NAME      READY   STATUS    RESTARTS   AGE    IP           NODE                 NOMINATED NODE   READINESS GATES
curlpod   1/1     Running   0          5m9s   10.244.0.6   kind-control-plane   <none>           <none>
myapp     1/1     Running   0          118m   10.244.0.5   kind-control-plane   <none>           <none>

// ログイン
➜  kubernetes k exec --stdin --tty curlpod -- /bin/sh
~ $ curl 10.244.0.5:8080
Hello, world!~ $

k port-forward <pod名> <転送先port>:<転送元port>

➜  kubernetes k port-forward myapp 5555:8080
Forwarding from 127.0.0.1:5555 -> 8080
Forwarding from [::1]:5555 -> 8080

Handling connection for 5555

// リクエストを投げる
➜  ~ curl localhost:5555
Hello, world!%
➜  ~

// pod ここ、deploy serviceなどでもできそう
kubectl edit pod myapp

apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: httpserver
  labels:
    app: httpserver
spec:
  replicas: 3
  selector:
    matchLabels:
      app: httpserver
  template:
    metadata:
      labels:
        app: httpserver
    spec:
      containers:
      - name: nginx
        image: nginx:1.25.3

 k apply --filename replocaset.yml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.24.0
        ports:
        - containerPort: 80

k apply --filename deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx --templeteのlabelsと一致している必要があるらしい
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.24.0
        ports:
        - containerPort: 80

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 10
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.24.0
        ports:
        - containerPort: 80
        lifecycle:
          preStop:
            exec:
              command: ["/bin/sh", "-c", "sleep 10"]

// podの監視
k get pod --watch

// podを削除する


➜  kubernetes k delete pod nginx-deployment-58556b4d6b-29pvc
pod "nginx-deployment-58556b4d6b-29pvc" deleted

// Terminatting されていることがわかる。新たに、nginx-deployment-58556b4d6b-65qs2 が作成されてpodの数が保たれる

nginx-deployment-58556b4d6b-g2gl8   1/1     Running             0          1s
nginx-deployment-58556b4d6b-hfm5p   1/1     Running             0          1s
nginx-deployment-58556b4d6b-29pvc   1/1     Terminating         0          21s
nginx-deployment-58556b4d6b-65qs2   0/1     Pending             0          0s
nginx-deployment-58556b4d6b-65qs2   0/1     Pending             0          0s
nginx-deployment-58556b4d6b-65qs2   0/1     ContainerCreating   0          0s
nginx-deployment-58556b4d6b-65qs2   1/1     Running

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

apiVersion: v1
kind: Service
metadata:
  name: hello-server-service
spec:
  selector:
    app: hello-server
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 8080

// deployment 実行
k apply --filename hello-server.yaml

// service

 k apply --filename service.yaml

## port-foward => pod か serviceか指定可能でserviceの場合は svc/のプレフィックスが必要
➜  kubernetes k port-forward svc/hello-server-service 8080:8080
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080

curl http://localhost:8080/

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-server
  labels:
    app: hello-server
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hello-server
  template:
    metadata:
      labels:
        app: hello-server
    spec:
      containers:
      - name: hello-server
        image: blux2/hello-server:1.4
        env:
        - name: PORT
          valueFrom:
            configMapKeyRef:
              name: hello-server-configmap
              key: PORT
---
apiVersion: v1
kind: ConfigMap // kindはここでConfigMap
metadata:
  name: hello-server-configmap
data:
  PORT: "8081"

---
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.5
        volumeMounts:
        - name: hello-server-config
          mountPath: /etc/config
      volumes:
      - name: hello-server-config
        configMap:
          name: hello-server-configmap
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: hello-server-configmap
data:
  myconfig.txt: |-
    I am hungry.

startupProbe:
  httpGet:
    path: /healthz
    port: 8080
  failureThreshold: 30
  periodSeconds: 10

readinessProbe:
  httpGet:
    path: /ready
    port: 8080
  periodSeconds: 5
  failureThreshold: 3

livenessProbe:
  httpGet:
    path: /healthz
    port: 8080
  initialDelaySeconds: 30
  periodSeconds: 10

apiVersion: v1
kind: Pod
metadata:
  labels:
    app: hello-server
  name: hello-server
spec:
  containers:
  - name: hello-server
    image: blux2/hello-server:1.6
    resources:
      requests:
        memory: "64Mi"
        cpu: "10m"
      limits:
        memory: "64Mi"
        cpu: "10m"

---
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:
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 1
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  values:
                  - hello-server
                  operator: In
              topologyKey: kubernetes.io/hostname
      containers:
      - name: hello-server
        image: blux2/hello-server:2.0.1
        env:
        - name: PORT
          valueFrom:
            configMapKeyRef:
              name: hello-server-configmap
              key: PORT
        resources:
          requests:
            memory: "256Mi"
            cpu: "10m"
          limits:
            memory: "256Mi"
            cpu: "10m"
        readinessProbe:
          httpGet:
            path: /healthz
            port: 8082
          initialDelaySeconds: 5
          periodSeconds: 5
        livenessProbe:
          httpGet:
            path: /healthz
            port: 8082
          initialDelaySeconds: 10
          periodSeconds: 5
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: hello-server-configmap
data:
  PORT: "8082"
  HOST: "localhost"
---
apiVersion: v1
kind: Service
metadata:
  name: hello-server-external
spec:
  type: NodePort
  selector:
    app: hello-server
  ports:
    - port: 8082
      targetPort: 8082
      nodePort: 30599
---
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: hello-server-pdb
spec:
  maxUnavailable: 10%
  selector:
    matchLabels:
      app: hello-server

10.0.0.0/24
10.0.0.[0-255] の範囲が1つのネットワーク

10.0.1.1  ← AWSのデフォルトゲートウェイ
10.0.1.4  ← フロント用EC2
10.0.1.5  ← API用EC2
10.0.1.6  ← RDS (自動割当)

flowchart LR
user[Browser/Client] -->|HTTP 80->8080| ecs_task[ECS Task go API]

subgraph VPC
subgraph PublicSubnet
ecs_task
sg[SG 8080 open]
end
rt[RouteTable 0.0.0.0/0 -> IGW]
igw[IGW]
end

%% ECSタスクからのログ送信
ecs_task -->|IAM Role: log write| cw[CloudWatch Logs]

%% ECRからのイメージプル
igw --> ecr[ECR Container Image]
ecs_task <-.-> igw
ecs_task -.pull image.-> ecr

%% 関連性
sg -. applied to ENI .-> ecs_task
rt --> igw

flowchart LR
    user[User sample-domain.com] --> route53[Route 53<br>Hosted Zone]
    route53 -->|Aレコード ALIAS| alb[ALB<br>example.com]
    alb -->|Target group| ecs[ECS Task<br>WordPress/Go API]
    ecs -->|IAM Role: log write| cw[CloudWatch Logs]

    subgraph VPC
      subgraph PublicSubnet
        alb
        ecs
        sg[SG 80/8080 open]
      end
      rt[RouteTable 0.0.0.0/0 -> IGW]
      igw[IGW]
    end

    %% ECR image pull
    igw --> ecr[ECR Container Image]
    ecs <-.-> igw
    ecs -.pull image.-> ecr

    %% SG適用
    sg -. applied to ENI .-> ecs
    rt --> igw

    %% 外部ドメイン
    domain_registrar[お名前.com<br>ドメイン取得]
    domain_registrar -->|ネームサーバ設定| route53

resource "aws_vpc" "main" {
  cidr_block = "10.0.0.0/16"
  tags = { Name = "ecs-test-go"}
}

resource "aws_subnet" "public" {
  vpc_id = aws_vpc.main.id
  cidr_block = "10.0.1.0/24"
  availability_zone = "ap-northeast-1a"
  tags = { Name: "ecs-test-go-public-subnect"}
}

resource "aws_internet_gateway" "igw" {
  vpc_id = aws_vpc.main.id
  tags = { Name = "ecs-test-go-igw" }
}

// ルートテーブル iwgを紐付ける
resource "aws_route_table" "public" {
  vpc_id = aws_vpc.main.id

  route {
    cidr_block = "0.0.0.0/0"
    gateway_id = aws_internet_gateway.igw.id
  }

  tags = { Name = "ecs-test-go-public-rt" }
}
resource "aws_security_group" "ecs_sg" {
  vpc_id = aws_vpc.main.id
  name   = "ecs-service-sg"

  ingress {
    from_port   = 8080
    to_port     = 8080
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }

  egress {
    from_port   = 0
    to_port     = 0
    protocol    = "-1"
    cidr_blocks = ["0.0.0.0/0"]
  }
}

// サブネットとルートテーブルを紐づける
// このサブネットに属する リソースは インターネットに接続できる
resource "aws_route_table_association" "public_assoc" {
  subnet_id      = aws_subnet.public.id
  route_table_id = aws_route_table.public.id
}

resource "aws_ecs_cluster" "main" {
  name = "ecs-test-go-cluster"
}

# resource "aws_iam_role" "ecs_task_execution_role" {
#   name = "ecsTaskExecutionRole"

#   assume_role_policy = jsonencode({
#     Version = "2012-10-17",
#     Statement = [{
#       Effect = "Allow",
#       Principal = {
#         Service = "ecs-tasks.amazonaws.com"
#       },
#       Action = "sts:AssumeRole"
#     }]
#   })
# }

# resource "aws_iam_role_policy_attachment" "ecs_task_execution_policy" {
#   role       = aws_iam_role.ecs_task_execution_role.name
#   policy_arn = "arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy"
# }

data "aws_iam_role" "ecs_task_execution_role" {
  name = "ecsTaskExecutionRole"
}

resource "aws_ecs_task_definition" "go_task" {
  family                   = "go-app-task"
  requires_compatibilities = ["FARGATE"]
  network_mode             = "awsvpc"
  cpu                      = "256"
  memory                   = "512"
  # execution_role_arn       = aws_iam_role.ecs_task_execution_role.arn

  execution_role_arn       = data.aws_iam_role.ecs_task_execution_role.arn


  container_definitions = jsonencode([
    {
      name      = "go-app"
      image     = "xxxxx.dkr.ecr.ap-northeast-1.amazonaws.com/ecs_test_go:latest"
      essential = true
      portMappings = [
        {
          containerPort = 8080
          hostPort      = 8080
        }
      ]
      
      logConfiguration = {
      logDriver = "awslogs",
      options = {
        "awslogs-group"         = "/ecs/go-app"
        "awslogs-region"        = "ap-northeast-1"
        "awslogs-stream-prefix" = "ecs"
      }
    }
    }
  ])
}

resource "aws_cloudwatch_log_group" "ecs" {
  name              = "/ecs/go-app"
  retention_in_days = 7
}

resource "aws_ecs_service" "go_service" {
  name            = "go-app-service"
  cluster         = aws_ecs_cluster.main.id
  task_definition = aws_ecs_task_definition.go_task.arn
  desired_count   = 1
  launch_type     = "FARGATE"

  network_configuration {
    subnets         = [aws_subnet.public.id]
    assign_public_ip = true
    security_groups =  [aws_security_group.ecs_sg.id]
  }
}

name: Deploy to ECS

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
      # リポジトリをチェックアウト
      - name: Checkout
        uses: actions/checkout@v4

      # AWS CLI をセットアップ
      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          aws-region: ap-northeast-1

      # Docker build & push to ECR
      - name: Log in to Amazon ECR
        id: login-ecr
        run: |
          aws ecr get-login-password --region ap-northeast-1 | \
          docker login --username AWS --password-stdin 123456789012.dkr.ecr.ap-northeast-1.amazonaws.com

      - name: Build, tag, and push image to Amazon ECR
        run: |
          IMAGE_TAG=latest
          ECR_REPO=123456789012.dkr.ecr.ap-northeast-1.amazonaws.com/myapp
          docker build -t $ECR_REPO:$IMAGE_TAG .
          docker push $ECR_REPO:$IMAGE_TAG

      # タスク定義ファイルの更新
      - name: Register new task definition
        run: |
          sed -e "s|<IMAGE>|123456789012.dkr.ecr.ap-northeast-1.amazonaws.com/myapp:latest|" ecs-task-def.json > new-task-def.json
          aws ecs register-task-definition --cli-input-json file://new-task-def.json

      # ECS サービス更新 (最新タスクでデプロイ)
      - name: Update ECS service
        run: |
          aws ecs update-service \
            --cluster my-cluster \
            --service my-service \
            --force-new-deployment

{
  "family": "my-task",
  "networkMode": "awsvpc",
  "requiresCompatibilities": ["FARGATE"],
  "cpu": "256",
  "memory": "512",
  "containerDefinitions": [
    {
      "name": "myapp",
      "image": "<IMAGE>",
      "essential": true,
      "portMappings": [
        {
          "containerPort": 8080,
          "protocol": "tcp"
        }
      ]
    }
  ],
  "executionRoleArn": "arn:aws:iam::123456789012:role/ecsTaskExecutionRole"
}