---
title: "DINA (@cisel) | Hashnode"
description: "DevOps team. Read the latest articles by DINA on Hashnode."
url: "https://hashnode.com/@cisel"
---

@cisel

# DINA

@cisel · Switzerland · Joined December 2020

DevOps team

[Website](https://www.dina.ch/)

## Comments

[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](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129/comment/61919370770afc563f667c00#reply-6195153390fac127e6ea4f0a)

Reply · Article · Nov 17, 2021 · [Push your Docker containers from GitLab to Amazon ECR](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129)

[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](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129/comment/61210b35e404793819ca9692#reply-612c841e2858872661b9cda2)

Reply · Article · Aug 30, 2021 · [Push your Docker containers from GitLab to Amazon ECR](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129)

[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.](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60d056e0d213af500c5d2ce5)

Reply · Article · Jun 21, 2021 · [Install Ansible AWX on Microk8s](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427)

[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](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60cb36688ce4491f0f298992)

Reply · Article · Jun 17, 2021 · [Install Ansible AWX on Microk8s](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427)

[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](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427/comment/60c0fe92d2660e41762e4445#reply-60c2f501a25fa357af83ed7e)

Reply · Article · Jun 11, 2021 · [Install Ansible AWX on Microk8s](https://hashnode.com/posts/install-ansible-awx-on-microk8s/60a25e0623723215ec2ff427)

[ub1k Thank's for sharing !](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129/comment/6077935f4155da32fc83b4bd#reply-60a4c86959b7dc409c3d2d98)

Reply · Article · May 19, 2021 · [Push your Docker containers from GitLab to Amazon ECR](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129)

[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](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129/comment/609717031ea29f2c341e08e8#reply-60a25848b66a0b15ebfcb58a)

Reply · Article · May 17, 2021 · [Push your Docker containers from GitLab to Amazon ECR](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129)

[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](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129/comment/6077935f4155da32fc83b4bd#reply-6087c6b4b81aa72681392895)

Reply · Article · Apr 27, 2021 · [Push your Docker containers from GitLab to Amazon ECR](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129)

[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](https://hashnode.com/posts/deploy-argocd-and-a-first-app-on-kubernetes/5ffda3a2b00f7510ee957de6/comment/600004a8b00f7510ee95a09d#reply-6000090dc162d710c9b14d7a)

Reply · Article · Jan 14, 2021 · [Deploy ArgoCD and a first App on Kubernetes](https://hashnode.com/posts/deploy-argocd-and-a-first-app-on-kubernetes/5ffda3a2b00f7510ee957de6)

[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.](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129/comment/5ffc78fba538d001351571cf#reply-5ffd75cb14d2f06c78ddf685)

Reply · Article · Jan 12, 2021 · [Push your Docker containers from GitLab to Amazon ECR](https://hashnode.com/posts/push-your-docker-containers-from-gitlab-to-amazon-ecr/5ffc7523aa5c467fe155b129)
