https://github.com/cb0n3y/ops-to-devops
DevOps journey lab with Vagrant, Prometheus, Grafana, Jenkins, CI/CD, Kubernetes, and IaaC. From sysadmin roots to modern DevOps practices.
https://github.com/cb0n3y/ops-to-devops
alerting ansible ci-cd devops devops-labs grafana home-lab iaac infrastructure-as-code jenkins kubernetes monitoring prometheus sysadmin-to-devops terraform vagrant
Last synced: 3 months ago
JSON representation
DevOps journey lab with Vagrant, Prometheus, Grafana, Jenkins, CI/CD, Kubernetes, and IaaC. From sysadmin roots to modern DevOps practices.
- Host: GitHub
- URL: https://github.com/cb0n3y/ops-to-devops
- Owner: cb0n3y
- License: mit
- Created: 2025-06-04T13:33:31.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2025-06-26T15:34:12.000Z (3 months ago)
- Last Synced: 2025-06-26T15:35:16.543Z (3 months ago)
- Topics: alerting, ansible, ci-cd, devops, devops-labs, grafana, home-lab, iaac, infrastructure-as-code, jenkins, kubernetes, monitoring, prometheus, sysadmin-to-devops, terraform, vagrant
- Language: Shell
- Homepage:
- Size: 130 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
README
# Ops to DevOps
Welcome to the **Ops to DevOps** repository! This project documents my journey transitioning from a System Administrator to a DevOps Engineer, showcasing the skills, tools, and projects I've developed along the way.
---
## 🧩 Current Focus
- Modular Vagrantfiles for Grafana and Prometheus
- Shared and app-specific setup scripts
- Gradual migration to Ansible for automation
- Terraform-based IaaC and Cloud automation (coming soon)
---
## 🏁 Long-Term Goals
- Build a clean, reproducible DevOps lab environment
- Prepare for certifications (CKA, AZ-104)
- Showcase end-to-end CI/CD, monitoring, and IaC solutions
- Follow open-source and GitHub community standards
---
## 📌 Topics Covered
- 🧱 Infrastructure as Code (Vagrant → Ansible → Terraform)
- 🔍 Monitoring & Observability (Prometheus, Grafana)
- ⚙️ Automation & Configuration
- 🚀 CI/CD Pipelines (GitHub Actions, Jenkins)
- 📦 Containerization & Kubernetes
- 🔐 Security, Documentation, and Collaboration
> ⚠️ This repo is a living lab — expect work-in-progress, breaking changes, and ongoing refinements as learning evolves.
---
## 📑 Table of Contents
- [Repository Structure](#repository-structure)
- [Lab](#lab)
- [IaaC](#iaac)
- [Deployment Strategy](#deployment-strategy)
- [Getting Started](#getting-started)
- [Contributing](#contributing)
- [License](#license)
---
## Repository Structure
The repository is organized into two main sections:
- **Lab/**: Hands-on configurations, scripts, and documentation related to various DevOps tools and technologies.
- **IaaC/**: Infrastructure as Code examples, including tools such as Vagrant, Ansible, Terraform, and others. These projects demonstrate infrastructure provisioning, automation, and environment management.
---
## Lab
This section includes:
- **Ansible**: Playbooks and roles for automation.
- **Bash**: Scripts for various administrative tasks.
- **Python**: Automation and utility scripts.
- **Docker**: Containerization setups.
- **Kubernetes**: Deployment configurations.
- **CI/CD**: Continuous Integration and Deployment pipelines.
- **Monitoring**: Tools and configurations for system monitoring.
- **Security**: Implementations to ensure system integrity.
- **Networking**: Configurations and scripts related to network management.
> Each subfolder contains a `README.md` with detailed information and usage instructions.
---
## IaaC
The IaaC/ directory represents a complete infrastructure setup, structured into different environments:
- **base/**: Shared configurations across all environments.
- **staging/**: Environment for testing and validation.
- **production/**: Live environment configurations.
Each environment includes:
- **applications/**: Deployed applications.
- **configs/**: Configuration files.
- **monitoring/**: Monitoring setups.
- **security/**: Security implementations.
---
## Deployment Strategy
Deployments are managed using Git tags:
- **`vX.Y.Z`**: Deploys to production.
- **`vX.Y.Z-beta`**: Deploys to staging.
Automated pipelines ensure smooth and consistent deployments across environments.
---
## Getting Started
To explore this repository:
1. **Clone the repository**:
```bash
git clone https://github.com/cb0n3y/ops-to-devops.git
cd ops-to-devops
2. **Navigate through the directories** to explore various tools, configurations, and projects
3. **Refer to individual** README.md files within each folder for detailed instructions and information.
## Contributing
This repository is primarily a personal portfolio, but community contributions and feedback are welcome.
Feel free to open an issue or submit a pull request for improvements or fixes.
## License
This project is licensed under the MIT License.