MKA1 enforces a deterministic supply chain where every container image is traceable to a specific source commit, built exclusively through automated CI pipelines, and stored in private registries that reject external artifacts.Documentation Index
Fetch the complete documentation index at: https://docs.mka1.com/llms.txt
Use this file to discover all available pages before exploring further.
What is active
Immutable artifact tagging
Every container image built by the platform is tagged with the originating git commit SHA. This creates an immutable, one-to-one link between source code and the deployed binary:- Images are pushed to Amazon ECR with commit-SHA tags (e.g.,
sha-a1b2c3d), ensuring each artifact is uniquely identifiable. - ECR repositories are configured as private registries scoped to the organization’s AWS account.
- ECR lifecycle policies enforce a 30-day retention window for commit-SHA images, keeping only the
latesttag indefinitely.
Controlled CI/CD pipeline
All container images originate from GitHub Actions workflows — no manual image pushes are permitted:- Deployment workflows authenticate with AWS via OIDC federation (no long-lived credentials).
- GitHub Actions use pinned action versions for reproducible, deterministic builds.
- Docker Buildx produces multi-platform images from a consistent build environment.
- Dependency integrity is verified during builds (e.g.,
go mod verifyfor Go modules). - Private module access is controlled via scoped GitHub PATs rather than broad credentials.
Private registry enforcement
Kubernetes deployments pull images exclusively from our private Amazon ECR registries:- All service manifests reference fully-qualified ECR image URIs within the organization’s AWS account.
- No public or third-party registries are referenced in production workloads.
- ECR native vulnerability scanning is enabled, providing automated assessment of image contents.
Secrets and key management
- All secrets are encrypted at rest using SOPS with a customer-managed AWS KMS key.
- Secrets are never stored in plaintext in the repository or in CI logs.
- Kubernetes cluster access is governed by IAM-integrated RBAC, restricting who can interact with workloads and registries.