#ECR
3 posts
K8s Practice #4: CI/CD Pipeline — GitHub Actions / ECR / ArgoCD
The `myshop-api` built in [#3](/en/posts/k8s-practice-3) still relies on manual steps whenever a new version is released. This post automates that process. GitHub Actions pushes container images to AWS ECR via OIDC without static keys, auto-commits Helm values in the manifest repo so the ArgoCD covered in [Advanced #6](/en/posts/k8s-advanced-6) can detect the change and sync to the cluster, and keeps PR approval gates, dev/prod branching, and canary deployment in one flow.
Docker in Practice #5 Pushing to Registries and Tag Strategy — The :latest Trap
Picking a registry (GHCR vs Docker Hub vs ECR) and tag strategy. Why :latest is dangerous in production, where semver and SHA tags belong, immutable tags, retention policies, and image size management — sorting out what comes after the push.
AWS Advanced #2: ECR — Image Registry
Amazon ECR private / public, IAM auth, docker push / pull, image scanning, lifecycle policies, multi-architecture (linux/amd64 + arm64) — where the images that ECS and Lambda will pull actually live.