---
title: "Comment by jan on \"Install Ansible AWX on Microk8s\" | Hashnode"
description: "should I ignore the following errors? kubectl apply -f awxconfig.yaml error: error validating &quot;awxconfig.yaml&quot;: error validating data: [ValidationErro"
url: "https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445"
---

[Discussion](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427)

Comment [Install Ansible AWX on Microk8s](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427)

[jan](https://hashnode.com/@jan66)

[Jun 9, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445)

should I ignore the following errors?

kubectl apply -f awxconfig.yaml error: error validating "awxconfig.yaml": error validating data: \[ValidationError(AWX.spec): unknown field "tower\_create\_preload\_data" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_hostname" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_image\_pull\_policy" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_ingress\_type" in com.ansible.awx.v1beta1.AWX.spec\]; if you choose to ignore these errors, turn validation off with --validate=false

[DINA](https://hashnode.com/@cisel)

[Jun 11, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60c2f501a25fa357af83ed7e)

Hi Jan,

No you can't ignore these validation errors. Have you created the AWX operator before with the command below?

```
microk8s kubectl apply -f https://raw.githubusercontent.com/ansible/awx-operator/devel/deploy/awx-operator.yaml
```

[Pete Scudamore](https://hashnode.com/@scud)

[Jun 16, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60ca72658ce4491f0f297632)

[CISEL](https://hashnode.com/@cisel)

I am encountering the identical issue.

microk8s kubectl apply -f [raw.githubusercontent.com/ansible/awx-operator/de…](https://raw.githubusercontent.com/ansible/awx-operator/devel/deploy/awx-operator.yaml) customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com created customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com created customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com created clusterrole.rbac.authorization.k8s.io/awx-operator created clusterrolebinding.rbac.authorization.k8s.io/awx-operator created serviceaccount/awx-operator created deployment.apps/awx-operator created

kubectl apply -f awxconfig.yaml error: error validating "awxconfig.yaml": error validating data: \[ValidationError(AWX.spec): unknown field "tower\_create\_preload\_data" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_hostname" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_image\_pull\_policy" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_ingress\_tls\_secret" in com.ansible.awx.v1beta1.AWX.spec, ValidationError(AWX.spec): unknown field "tower\_ingress\_type" in com.ansible.awx.v1beta1.AWX.spec\]; if you choose to ignore these errors, turn validation off with --validate=false

[DINA](https://hashnode.com/@cisel)

[Jun 17, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60cb36688ce4491f0f298992)

[Pete Scudamore](https://hashnode.com/@scud) [jan](https://hashnode.com/@jan66) Hi!

Ok I understand now... The Operatorl URL is wrong...

Sorry Guys!!!

I have edited the post with the right URL but below you will find the URL for the Operator with version 0.9.0 [raw.githubusercontent.com/ansible/awx-operator/0.…](https://raw.githubusercontent.com/ansible/awx-operator/0.9.0/deploy/awx-operator.yaml)

The TAG version was missing in the URL

[Pete Scudamore](https://hashnode.com/@scud)

[Jun 17, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60cb774fe60a1f300380e785)

[CISEL](https://hashnode.com/@cisel)

The updated awx operator path worked! I ran into another problem further down.

scud@erebor:~$ helm install ingress nginx-stable/nginx-ingress --namespace kube-system Error: Kubernetes cluster unreachable: Get "[localhost/version](http://localhost:8080/version?timeout=32s%22:) dial tcp 127.0.0.1:8080: connect: connection refused

Here is what my pod networking looks like after getting to this part of the install: kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES awx-operator-5595d6fc57-jfqvh 1/1 Running 0 10m 10.1.5.4 erebor <none> <none> awx-postgres-0 1/1 Running 0 7m18s 10.1.5.5 erebor <none> <none> awx-5b58db49c-j6gxc 4/4 Running 0 7m9s 10.1.5.6 erebor <none> <none>

I was wondering if I was supposed to change any of the IP addressing in the MetalLB section. I am not sure how the 192.x addressing is relevant, and if it is related to this issue.

netstat -an |grep 8080 tcp 0 0 10.0.1.1:51778 10.1.5.2:8080 TIME\_WAIT

[DINA](https://hashnode.com/@cisel)

[Jun 21, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60d056e0d213af500c5d2ce5)

[Pete Scudamore](https://hashnode.com/@scud) It seems that the Helm client is unable to connect to the Kubernetes cluster API. What happens if you simply run the helm list command? It should return

```
~$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
```

The Pods seem to be correct, here is what our test environment looks like. (Sorry but I can't actually upload the image on Hashnode, it failed each time...)

```
xxxxxxx@CISEL-CG92373NY:~$ kubectl get pods
NAME                            READY   STATUS    RESTARTS   AGE
awx-operator-5595d6fc57-wrgq4   1/1     Running   3          39d
awx-79d94fd5fb-slp59            4/4     Running   12         39d
awx-postgres-0                  1/1     Running   3          39d
xxxxxxx@CISEL-CG92373NY:~$ kubectl get pod -o wide
NAME                            READY   STATUS    RESTARTS   AGE   IP            NODE         NOMINATED NODE   READINESS GATES
awx-operator-5595d6fc57-wrgq4   1/1     Running   3          39d   10.1.130.15   xxxxxxx   <none>           <none>
awx-79d94fd5fb-slp59            4/4     Running   12         39d   10.1.130.6    xxxxxxx   <none>           <none>
awx-postgres-0                  1/1     Running   3          39d   10.1.130.9    xxxxxxx   <none>           <none>
xxxxxxx@CISEL-CG92373NY:~$ kubectl get service
NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
kubernetes             ClusterIP   10.152.183.1     <none>        443/TCP             62d
awx-operator-metrics   ClusterIP   10.152.183.241   <none>        8383/TCP,8686/TCP   39d
awx-postgres           ClusterIP   None             <none>        5432/TCP            39d
awx-service            NodePort    10.152.183.120   <none>        80:31298/TCP        39d
xxxxxxx@CISEL-CG92373NY:~$ kubectl get ingress
NAME          CLASS    HOSTS                     ADDRESS         PORTS     AGE
awx-ingress   <none>   xxxxxxx.cisel.ch   172.20.11.159   80, 443   62d
```

And MetalLB config

```
xxxxxxx@CISEL-CG92373NY:~$ kubectl -n metallb-system describe cm config
Name:         config
Namespace:    metallb-system
Labels:       <none>
Annotations:  <none>

Data
====
config:
----
address-pools:
- name: default
  protocol: layer2
  addresses:
  - 172.20.11.159-172.20.11.162

Events:  <none>
xxxxxxx@CISEL-CG92373NY:~$
```

As for the IP range in MetalLB, you need to use the same subnet as your server or workstation.

[Pete Scudamore](https://hashnode.com/@scud)

[Jul 2, 2021](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60df597603707d644a4ff051)

[CISEL](https://hashnode.com/@cisel)

I got everything going. I had to install helm. I also had to add a command to get helm to see the kubernetes cluster properly.

kubectl config view --raw >~/.kube/config # fix to helm cant find cluster issue

Thanks for the great article!
