DiaryFolio

Summary Traditional CI/CD tools like GitHub Actions, GitLab CI/CD, and Azure DevOps (ADO) offer powerful pipeline features, but they often tightly couple your automation logic to their platforms. This creates a problem when switching tools or scaling across teams. By using Ansible as the central workflow engine—and treating GitHub, GitLab, or ADO as lightweight orchestrators—you can build a modular, portable CI/CD system. This hybrid approach enables tool-agnostic pipelines and promotes reuse across projects and platforms. Why Use Ansible in CI/CD? Portability: Move your pipeline between GitHub, GitLab, or ADO without rewriting core logic. Modularity: Write Ansible playbooks for each stage (build, test, deploy) and reuse them across environments. Maintainability: Keep your workflow logic in version-controlled, testable, and readable YAML files. Tool Independence: Avoid vendor lock-in by abstracting workflow logic into a standalone orchestration ...

  Deploying awx into kubernetes Intro AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. This article will summarise steps of installing AWX into Kubernetes using Operator Pre-Reqs Familiarity with Kubernetes (k8s) Bit powerful node machine of 4vCPU & 8GB RAM AWX is exposed on port 9080, so enable firewall accordingly (As default port 80 will have collision mostly in a Kubernetes environment) Build Operator from code (Optional Step) Unfortunately at the time of writing, the official repository doesn't give a operator yaml directly, but suggests to build from code. But we use a pre-built operator yaml and hence below step of creating from source-code is optional apiVersion: v1 kind: PersistentVolumeClaim metadata: creationTimestamp: null labels: io.kompose.service: n8n-claim0 name: n8n-claim0 spec: accessModes: - ReadWriteOnce resources: requests: storage: 2Gi status: {} Package components The deployment i...