Add README files and diagrams across repository
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
# labs
|
||||
|
||||
This directory collects hands-on lab areas used for experimentation and skill development. It complements the production-style tooling elsewhere in the repository by separating exploratory work from operational examples.
|
||||
|
||||
## Diagram
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A["labs"] --> B["docker"]
|
||||
A --> C["kubernetes"]
|
||||
A --> D["terraform"]
|
||||
A --> E["networking"]
|
||||
A --> F["ci-cd"]
|
||||
```
|
||||
|
||||
## Scope
|
||||
|
||||
- `docker` - container runtime and image workflow practice.
|
||||
- `kubernetes` - orchestration and workload experiments.
|
||||
- `terraform` - infrastructure-as-code exercises.
|
||||
- `networking` - connectivity and protocol-focused labs.
|
||||
- `ci-cd` - pipeline and delivery automation practice.
|
||||
|
||||
## Notes
|
||||
|
||||
- These folders are intentionally separate from `infra-run` to keep experiments isolated from the operational core.
|
||||
@@ -0,0 +1,18 @@
|
||||
# labs/ci-cd
|
||||
|
||||
This folder is intended for CI/CD experiments such as pipeline layouts, validation jobs, artifact flows, and deployment automation patterns.
|
||||
|
||||
## Diagram
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
A["ci-cd"] --> B["Build"]
|
||||
A --> C["Test"]
|
||||
A --> D["Package"]
|
||||
A --> E["Deploy"]
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- The directory is currently a placeholder.
|
||||
- It provides a dedicated area for delivery automation concepts outside the main operations toolkits.
|
||||
@@ -0,0 +1,17 @@
|
||||
# labs/docker
|
||||
|
||||
This folder is reserved for Docker-focused lab work. It is intended for image builds, container runtime testing, compose workflows, and lightweight environment simulations.
|
||||
|
||||
## Diagram
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
A["docker"] --> B["Dockerfiles"]
|
||||
A --> C["Compose stacks"]
|
||||
A --> D["Container debugging"]
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- The directory currently contains only a placeholder file.
|
||||
- It represents a sandbox for container workflows rather than finalized portfolio tooling.
|
||||
@@ -0,0 +1,18 @@
|
||||
# labs/kubernetes
|
||||
|
||||
This folder is intended for Kubernetes lab work such as manifests, troubleshooting exercises, and orchestration experiments.
|
||||
|
||||
## Diagram
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
A["kubernetes"] --> B["Workloads"]
|
||||
A --> C["Services"]
|
||||
A --> D["Ingress and networking"]
|
||||
A --> E["Cluster troubleshooting"]
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- The directory is currently a placeholder.
|
||||
- It keeps orchestration experiments separate from the production-style script content.
|
||||
@@ -0,0 +1,18 @@
|
||||
# labs/networking
|
||||
|
||||
This folder is reserved for networking-focused exercises. It can hold examples around routing, DNS, ports, packet flow, and host-to-host diagnostics.
|
||||
|
||||
## Diagram
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
A["networking"] --> B["Routing"]
|
||||
A --> C["DNS"]
|
||||
A --> D["Firewall and ports"]
|
||||
A --> E["Connectivity tests"]
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- The directory is currently a placeholder.
|
||||
- It complements the operational network diagnostics already present in `infra-run/scripts/bash/os-healthcheck`.
|
||||
@@ -0,0 +1,17 @@
|
||||
# labs/terraform
|
||||
|
||||
This folder is intended for Terraform experiments and infrastructure-as-code practice. It is the natural place for module trials, state-handling examples, and environment provisioning exercises.
|
||||
|
||||
## Diagram
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
A["terraform"] --> B["Modules"]
|
||||
A --> C["Environment configs"]
|
||||
A --> D["Plan and apply workflows"]
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- The directory currently contains only a placeholder file.
|
||||
- It is positioned as a lab space rather than a production-ready IaC stack.
|
||||
Reference in New Issue
Block a user