Automated Kubernetes & OpenShift Lab

I’m setting up a production-like lab in AWS that hosts both Kubernetes and OpenShift clusters. My end goal is to spin up, reconfigure, or tear down this environment with a single command so I can reliably test Jenkins-driven CI/CD pipelines, observe system behaviour with Prometheus + Grafana, and iterate on Ansible-based infrastructure code without touching live workloads. Here’s the flow I have in mind: • Infrastructure lives in Git; a commit to the main branch should trigger Jenkins to call Ansible, which builds or updates the clusters and their supporting resources (VPC, subnets, security groups, IAM roles, EBS/EFS, Load Balancers). • Cluster bootstrapping automatically installs core operators, monitoring stack, logging, and basic ingress. • When the job completes, Jenkins reports back and publishes a short environment manifest so I can hand it to test engineers. • A separate Jenkins job tears the lab down cleanly. What I need from you – Idempotent Ansible playbooks/roles that cover AWS provisioning, cluster installation, and post-install configuration. – Jenkins pipeline files (declarative or scripted) that wire everything together with suitable stages, artefact handling, and notifications. – Documentation (README plus in-repo comments) so another DevOps engineer can extend or troubleshoot the setup. Acceptance criteria 1. Running “jenkins build LAB-CREATE” results in a ready-to-use Kubernetes and OpenShift lab reachable via public endpoints and kubeconfig files emitted as pipeline artefacts. 2. Monitoring dashboard URLs are included in the output and show live node metrics. 3. “jenkins build LAB-DESTROY” removes all AWS resources, leaving the account clean with no dangling EBS volumes or ELBs. 4. Re-running LAB-CREATE without code changes performs no-op updates (Ansible reports zero changes). If you have experience marrying Jenkins, Ansible, and AWS for container platforms and can deliver clean, reproducible code, I’d love to work together.

Projekt-ID: 40230445