Abdalrahman AttyaContainers · GitOps · Kubernetes
Container Delivery & GitOps
Two repositories make delivery ownership visible: one tests, scans, and publishes an immutable multi-architecture image; the other owns reviewed Kubernetes desired state and Argo CD reconciliation.
- Image
- Published multi-architecture v0.1.3
- Runtime
- Docker Desktop Kubernetes verified
- Boundary
- No managed-cloud or production claim
The delivery path
The application repository owns tests, non-root image construction, vulnerability scanning, an SBOM, and publication to GitHub Container Registry. The GitOps repository owns manifests, overlays, probes, security context, network policy, and reconciliation.
The handoff is an immutable image digest. Operational evidence includes diagnosis of a broken image, Git revert recovery, rollout checks, and endpoint verification.
Architecture
Separate application delivery from desired state
Engineering decisions
- Immutable handoff: deployment consumes a digest rather than a moving tag.
- Independent ownership: application and desired-state changes have separate review surfaces.
- Runtime controls: probes, security context, and network policy travel with the desired state.
- Recovery: rollback behavior is demonstrated rather than assumed.