Popular posts

Pete Scudamore jan 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.…

The TAG version was missing in the URL

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 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

Pete Scudamore 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.

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!