Focus on infrastructure as code, observability, and incident response to build DevOps credibility through measurable outcomes.

Actionable Workflow

1. Master Infrastructure as Code (IaC)

   • Start with Terraform for provisioning cloud resources (AWS/GCP/Azure) and OpenShift clusters.
   • Use Ansible for configuration management (e.g., ensuring consistent node setups).
   • Example: Write a Terraform script to spin up an OpenShift cluster, then use Ansible to deploy a test app.

2. Build Observability Muscle

   • Deploy Prometheus and Grafana for metrics collection and dashboards.
   • Set up alerts for critical issues (e.g., node failures, API server downtime).
   • Integrate logging with Elasticsearch and Kibana (EFK stack) or OpenShift’s built-in logging.

3. Own Incident Response

   • Volunteer for on-call rotations to gain hands-on experience.
   • Lead postmortems: Document root causes, assign action items, and track resolutions.
   • Use tools like PagerDuty for alert routing and incident tracking.

Policy Example: GitOps Deployment Workflow

Enforce a GitOps policy using ArgoCD or OpenShift Pipelines:

• All changes require a pull request (PR) with automated tests.
• Production deployments require manual approval via PR.
• Use OpenShift’s built-in GitOps to sync manifests from a repository.
• Example: Block deployments if unit tests fail or vulnerability scans detect critical CVEs.

Tooling Essentials

• Terraform: Provision infrastructure (clusters, networks, storage).
• Ansible: Automate configuration drift fixes.
• Prometheus/Grafana: Monitor cluster health and app performance.
• ArgoCD/OpenShift GitOps: Manage deployments via Git.
• Helm: Package Kubernetes applications.
• kubectl/oc:

Source thread: Switching from React Dev to DevOps—how do I not look like a fraud with 2 years exp?