# mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd architecture

> Architecture diagram of the GitHub repository mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-04-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd
- Repository: https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd

## Overview

1. This repository is a small CI/CD and deployment demo, not a large application codebase. The architecture centers on a simple static app, a container build pipeline, and Kubernetes deployment manifests.

2. The application layer is the `app/` directory. It contains an `index.html` and an `app/Dockerfile`, which suggests the runtime artifact is a containerized static web page or similarly simple frontend asset.

3. The build boundary is the Docker image. The Dockerfile in `app/` is the packaging step that turns the app content into an image that can run consistently anywhere a container runtime exists.

4. The CI boundary is `.github/workflows/docker-build.yml`. GitHub Actions is used to automate image creation, likely triggered by repository changes, and to publish the image to a registry such as Docker Hub, as described in the README.

5. The deployment boundary is the `k8s/` folder. `deployment.yaml` defines how the container should run in Kubernetes, including the pod template, container image reference, and replica management. `service.yaml` exposes that workload inside the cluster.

6. The runtime target is Kubernetes. The cluster is responsible for scheduling pods, keeping the desired replica count, and providing service discovery/network access through the Service object.

7. ArgoCD is part of the delivery model described in the README, but it is not represented as a file in this repository. Architecturally, it sits between Git and Kubernetes as the GitOps reconciliation layer that watches the manifest source and applies changes to the cluster.

8. The main data flow is: app source in `app/` → Docker image build via GitHub Actions → image pushed to Docker Hub → Kubernetes Deployment pulls the image → Service exposes the running pods → ArgoCD continuously syncs desired state from Git to the cluster.

9. The repository therefore separates concerns into three clear subsystems: application content, image build automation, and cluster deployment configuration. That separation is important for diagramming because each subsystem has a different lifecycle and actor.

10. External systems that materially affect the architecture are GitHub Actions, Docker Hub, Kubernetes, and ArgoCD. GitHub Actions handles CI, Docker Hub acts as the image registry, Kubernetes is the execution environment, and ArgoCD provides Git-driven deployment synchronization.

11. There are no visible databases, queues, APIs, or microservice boundaries in this repo. For an architecture diagram, this should be shown as a single deployable containerized web asset rather than a multi-service backend system.

12. In short, the repo demonstrates a minimal GitOps-style flow: source code is stored in Git, built into a container, published to a registry, and deployed to Kubernetes through manifest files that ArgoCD can reconcile.

Main entry points: [`k8s/deployment.yaml`](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/k8s/deployment.yaml) (Deployment), [`k8s/service.yaml`](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/k8s/service.yaml) (Service), [`app/Dockerfile`](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/tree/main/app/Dockerfile) (Dockerfile), [`.github/workflows/docker-build.yml`](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/.github/workflows/docker-build.yml) (Build workflow)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_application["Application"]
  node_app_source["App page<br/>static asset<br/>[index.html]"]
  node_dockerfile["Dockerfile<br/>image build spec"]
end

subgraph group_ci["CI Pipeline"]
  node_workflow["Build workflow<br/>GitHub Actions<br/>[docker-build.yml]"]
  node_image_build["Image build<br/>CI step"]
end

subgraph group_deployment["Kubernetes Delivery"]
  node_k8s_deploy["Deployment<br/>Kubernetes manifest<br/>[deployment.yaml]"]
  node_k8s_service["Service<br/>Kubernetes manifest<br/>[service.yaml]"]
end

subgraph group_external["External Systems"]
  node_registry[("Docker Hub<br/>registry")]
  node_git_repo(("Git repo<br/>source control"))
  node_argocd["ArgoCD<br/>GitOps reconciler"]
  node_cluster{{"Kubernetes<br/>runtime cluster"}}
end

node_app_source -->|"packaged by"| node_dockerfile
node_dockerfile -->|"used by"| node_image_build
node_workflow -->|"runs"| node_image_build
node_image_build -->|"pushes"| node_registry
node_git_repo -->|"triggers"| node_workflow
node_git_repo -->|"watched by"| node_argocd
node_argocd -->|"syncs"| node_k8s_deploy
node_k8s_deploy -->|"pulls image"| node_registry
node_k8s_deploy -->|"runs on"| node_cluster
node_k8s_service -->|"exposes"| node_cluster
node_k8s_service -->|"targets"| node_k8s_deploy

click node_app_source "https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/app/index.html"
click node_dockerfile "https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/tree/main/app/Dockerfile"
click node_workflow "https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/.github/workflows/docker-build.yml"
click node_k8s_deploy "https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/k8s/deployment.yaml"
click node_k8s_service "https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/k8s/service.yaml"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_app_source,node_dockerfile toneBlue
class node_workflow,node_image_build toneAmber
class node_k8s_deploy,node_k8s_service toneMint
class node_registry,node_git_repo,node_argocd,node_cluster toneRose
```

## Components

### Application

Static web app source and container packaging

- [App page](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/app/index.html): static asset · HTML content for the demo app · `app/index.html`
- [Dockerfile](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/tree/main/app/Dockerfile): image build spec · Packages the app into a container image · `app/Dockerfile`

### CI Pipeline

Automated image build and publish flow

- [Build workflow](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/.github/workflows/docker-build.yml): GitHub Actions · Automates container image build and publish · `.github/workflows/docker-build.yml`
- **Image build**: CI step · Turns app content into a runnable container image

### Kubernetes Delivery

Cluster manifests and runtime exposure

- [Deployment](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/k8s/deployment.yaml): Kubernetes manifest · Declares desired pod count and container image · `k8s/deployment.yaml`
- [Service](https://github.com/mdshafiurrahman0/deploying-a-simple-app-with-docker-github-actions-kubernetes-argocd/blob/main/k8s/service.yaml): Kubernetes manifest · Exposes the workload inside the cluster · `k8s/service.yaml`

### External Systems

Git hosting, registry, GitOps, and cluster runtime

- **Docker Hub**: registry · Stores the published container image
- **Git repo**: source control · Versioned source and manifest repository
- **ArgoCD**: GitOps reconciler · Syncs desired state from Git into the cluster
- **Kubernetes**: runtime cluster · Schedules pods and serves cluster networking

## Connections

- App page → Dockerfile: packaged by · Static content is included in the container image
- Dockerfile → Image build: used by · Build instructions drive image creation
- Build workflow → Image build: runs · GitHub Actions executes the build step
- Image build → Docker Hub: pushes · Built image is published to the registry
- Git repo → Build workflow: triggers · Repository changes start the CI workflow
- Git repo → ArgoCD: watched by · ArgoCD observes manifests in Git
- ArgoCD → Deployment: syncs · Desired state is applied from Git to Kubernetes
- Deployment → Docker Hub: pulls image · Deployment references the published container image
- Deployment → Kubernetes: runs on · Kubernetes schedules the pods
- Service → Kubernetes: exposes · Service provides cluster-internal access
- Service → Deployment: targets · Service selects pods from the deployment
