Skip to main content

Deploying awx into kubernetes


Deploying awx into kubernetes


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


  • 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
  creationTimestamp: null
    io.kompose.service: n8n-claim0
  name: n8n-claim0
    - ReadWriteOnce
      storage: 2Gi
status: {}

Package components

The deployment is split into following
  • awx-operator.yaml  - Pre-built operator file
  • awx-pvc0.yaml  - PersistentVolumeClaim To mount directory awx
  • awx-deployment.yaml  - Actual deployment definitions
  • awx-svc.yaml  - Service To expose awx for UI access


kubectl create ns awx
kubectl apply -f


 apiVersion: v1
 kind: PersistentVolumeClaim
   name: static-data-pvc
     - ReadWriteOnce
   storageClassName: local-path
       storage: 2Gi


kind: AWX
  name: awx
  service_type: LoadBalancer
  loadbalancer_port: 9080
  projects_persistence: true
  projects_storage_access_mode: ReadWriteOnce
  web_extra_volume_mounts: |
    - name: static-data
      mountPath: /var/lib/awx/public
  extra_volumes: |
    - name: static-data
        claimName: static-data-pvc


apiVersion: v1
kind: Service
  name: awx-svc1
  - port: 5432
    targetPort: 5432
    protocol: TCP
    name: awx-port
    app: awx
  type: LoadBalancer

Apply in following order

kubectl create ns awx # Might be already created
kubectl -n awx apply -f <operator> # Might be already done
kubectl -n awx apply -f awx-pvc0.yaml
kubectl -n awx apply -f awx-deployment.yaml
kubectl -n awx apply -f awx-svc.yaml
kubectl -n awx get all # To see all components
curl http://<cluster_ip>:9080

Popular posts from this blog

Create your own Passport Photo using GIMP

This tutorial is for semi-techies who knows a bit of GIMP (image editing).   This tutorial is for UK style passport photo ( 45mm x 35 mm ) which is widely used in UK, Australia, New Zealand, India etc.  This is a quick and easy process and one can create Passport photos at home If you are non-technical, use this link   .  If you want to create United States (USA) Passport photo or Overseas Citizen of India (OCI) photo, please follow this link How to Make your own Passport Photo - Prerequisite GIMP - One of the best image editing tools and its completely Free USB stick or any memory device to store and take to nearby shop A quality Digital camera Local Shops where you can print. Normally it costs (£0.15 or 25 US cents) to print 8 photos Steps (Video Tutorial attached blow of this page) Ask one of your colleague to take a photo  of you with a light background. Further details of how to take a photo  yourself       Take multiple pictures so that you can choose from th

Syslog Standards: A simple Comparison between RFC3164 & RFC5424

Syslog Standards: A simple Comparison between RFC3164 (old format) & RFC5424 (new format) Though syslog standards have been for quite long time, lot of people still doesn't understand the formats in detail. The original standard document is quite lengthy to read and purpose of this article is to explain with examples Some of things you might need to understand The RFC standards can be used in any syslog daemon (syslog-ng, rsyslog etc.) Always try to capture the data in these standards. Especially when you have log aggregation like Splunk or Elastic, these templates are built-in which makes your life simple. Syslog can work with both UDP & TCP  Link to the documents the original BSD format ( RFC3164 ) the “new” format ( RFC5424 ) RFC3164 (the old format) RFC3164 originated from combining multiple implementations (Year 2001)

VS Code & Portable GIT shell integration in Windows

Visual Studio Code & GIT Portable shell Integration Summary Many of your corporate laptop cannot install programs and it is quite good to have them as portable executables. Here we find a way to have Portable VS Code and Portable GIT and integrate the GIT shell into VS Code Pre-Reqs VS Code (Install version or Portable ) GIT portable Steps Create a directory in your Windows device (eg:  C:\installables\ ) Unpack GIT portable into the above directory (eg it becomes: C:\installables\PortableGit ) Now unpack Visual Studio (VS) Code and run it. The default shell would be windows based Update User or Workspace settings of VS Code (ShortCut is:  Control+Shift+p ) Update the settings with following setting { "workbench.colorTheme": "Default Dark+", "git.ignoreMissingGitWarning": true, "git.enabled": true, "git.path": "C:\\installables\\PortableGit\\bin\\git.exe", ""