Install and prepare MicroK8s
sudo snap install microk8s --classicYou need to run following commands. It allows you to run commands without needing sudo privileges:
sudo usermod -a -G microk8s $USER
sudo chown -f -R $USER ~/.kube
exitEnable necessary add-ons:
microk8s enable storage dns ingressCreate alias and you can use just kubectl:
sudo snap alias microk8s.kubectl kubectlClone from git awx-operator and deploy to MicroK8s:
git clone https://github.com/ansible/awx-operator.git
cd awx-operator
Check awx-operator releases by link below:
https://github.com/ansible/awx-operator/releases
Change branch for current release and deploy awx-operator:
git checkout 0.22.0
export NAMESPACE=ansible-awx
sudo apt install make
make deployWait while operator will be deployed and verifying with command below:
kubectl get pods -n $NAMESPACEYou have to see something like:
Create a YAML file with the following and Deploy AWX:
nano my-awx.yml
---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: awx-demo
spec:
service_type: nodeport
Apply yaml file:
kubectl apply -f my-awx.yml -n ansible-awxCheck status of deployment following commands:
kubectl get pods -n $NAMESPACE
watch kubectl get pods -l "[app.kubernetes.io/managed-by=awx-operator](http://app.kubernetes.io/managed-by=awx-operator)" -n ansible-awxYou have to see 4/4 containers running.
Let’s create Ingress file with following rule
nano my-awx-ingress.yml---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: awx-demo
spec:
service_type: nodeport
ingress_type: ingress
hostname: awx.test.me
And now apply new ingress settings:
kubectl apply -f my-awx-ingress.yml -n ansible-awxOnce a settings is applied you have opportunity to access AWX by 80 port.
The default username is admin. The password randomly generated. For this you need to do following command:
kubectl get secret awx-demo-admin-password -n ansible-awx -o jsonpath='{.data.password}' | base64 --decode
Greetings,
I have installed AWX on microk8s in ubuntu OS. After logging in to web UI of AWX, In projects I have selected SCM as manual but the warning error continued and as per steps mentioned by you in this page I have even created a yaml file and given all previleges to yaml files but no changes. Same warning error repeats. Can you please assist me in this.
Hello.) Could you show me your warning error? Or screenshots?
Hi,
I’ve followed this guide to the letter, but after I apply the ingress file, I get a 404 Error when trying to browse to the URL for the AWX UI.
Hi,
Check the ingress rule is applied correctly:
NAME CLASS HOSTS ADDRESS PORTS AGE awx.yourname.com 80, 443 4m53s)
awx-ingress
ubuntu@ip-172-31-0-208:~$ microk8s kubectl describe ingress
Name: awx-ingress
Namespace: default
Address:
Default backend: default-http-backend:80 (
TLS:
awx-secret-tls terminates awx.yourname.com
Rules:
Host Path Backends
—- —- ——–
awx.yourname.com
/ awx-service:80 (10.1.59.71:8052)
Annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1
Events:
ubuntu@ip-172-31-0-208:~$
The above looks ok, but there’s nothing under ‘Events’. If you set a hostname in /etc/hosts on the machine you are browsing from you will see an NGINX 404 not found message.
Remove and reapply the ingress – note that after that is done, the events list has a CREATE event in it:
ubuntu@ip-172-31-0-208:~$ microk8s kubectl delete -f myingress.yml)
ingress.networking.k8s.io “awx-ingress” deleted
ubuntu@ip-172-31-0-208:~$ microk8s kubectl apply -f myingress.yml
ingress.networking.k8s.io/awx-ingress created
ubuntu@ip-172-31-0-208:~$ microk8s kubectl describe ingress
Name: awx-ingress
Namespace: default
Address:
Default backend: default-http-backend:80 (
TLS:
awx-secret-tls terminates awx.yourname.com
Rules:
Host Path Backends
—- —- ——–
awx.yourname.com
/ awx-service:80 (10.1.121.71:8052)
Annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1
Events:
Type Reason Age From Message
—- —— —- —- ——-
Normal CREATE 3s nginx-ingress-controller Ingress default/awx-ingress
ubuntu@ip-172-31-0-208:~$
Make sure the hostname resolves on your computer, then browse to https://awx.yourname.com and you should see a login page (after you pass the invalid self-signed certificate warning).
I hope this helps someone else out!
https://dataplumber.wordpress.com/2021/04/22/installing-awx-19-on-microk8s-in-aws/