Hi Kavitha, Do you have docker on the image of your stage where you're trying to build your docker container ? Here we use a dind service (docker in docker) : publish : stage : build image : name : docker :latest services : - docker : 19 -dind Hope it helps ! Best regards

Hi RAMJOS ! Thank's for the comment ! Yes ofc, after putting the image in the repo, you can deploy it on Kubernetes. We have an other article for that : https://devops.cisel.ch/deploy-argocd-and-a-first-app-on-kubernetes Hope it helps ! Best regards

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-CG 92373 NY:~$ kubectl get pods NAME READY STATUS RESTARTS AGE awx -operator- 5595 d 6 fc 57 -wrgq 4 1 / 1 Running 3 39 d awx - 79 d 94 fd 5 fb-slp 59 4 / 4 Running 12 39 d awx -postgres- 0 1 / 1 Running 3 39 d xxxxxxx @CISEL-CG 92373 NY:~$ kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES awx -operator- 5595 d 6 fc 57 -wrgq 4 1 / 1 Running 3 39 d 10.1.130.15 xxxxxxx <none> <none> awx - 79 d 94 fd 5 fb-slp 59 4 / 4 Running 12 39 d 10.1.130.6 xxxxxxx <none> <none> awx -postgres- 0 1 / 1 Running 3 39 d 10.1.130.9 xxxxxxx <none> <none> xxxxxxx @CISEL-CG 92373 NY:~$ kubectl get service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.152.183.1 <none> 443 /TCP 62 d awx -operator-metrics ClusterIP 10.152.183.241 <none> 8383 /TCP, 8686 /TCP 39 d awx -postgres ClusterIP None <none> 5432 /TCP 39 d awx -service NodePort 10.152.183.120 <none> 80 : 31298 /TCP 39 d xxxxxxx @CISEL-CG 92373 NY:~$ kubectl get ingress NAME CLASS HOSTS ADDRESS PORTS AGE awx -ingress <none> xxxxxxx.cisel.ch 172.20.11.159 80 , 443 62 d 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 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 https://raw.githubusercontent.com/ansible/awx-operator/0.9.0/deploy/awx-operator.yaml The TAG version was missing in the URL

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

ub1k Thank's for sharing !

Hi, Are you sure that your env variables are populated correctly on the right repo (each repo needs to have it's own environment variables set up) ? Can you try in local with the command aws ecr get-login-password ? It would help you to find out the problem. Maybe you need to upgrade your awscli or maybe there is a problem with the --region. Hope it helps ! Best regards

Hi Lucas, Thank's for your comment. Did you try to run an aws configure and a login from a terminal to be sure that your access are ok ? Can you check that your variables are configured in the right gitlab project ? If it's the case, can you try to rename your variable in gitlab with an other name ? For example, rename AWS_ACCESS_KEY_ID to AMAZON_ACCESS_KEY_ID and try again to see if there is a difference in your error message. Hope it helps ! Best regards

Hi! Thanks for your comment! Yes of course we are using ArgoCD with Helm repo as source and that rocks! Do you have a specific question? BR

Thank you for your comments and suggestions. You are absolutely right! We thought that showing the various variables and the use of awscli in the code might help to better understand the process.