So we have been developing cloud formation templates for our training infrastructure needs and so far we were doing Smoke Testing. And now we need to test cloud formation templates in an automated fashion. So here is a solution for my use case but can be adapted.
In this guide we are using:
Sorry there is no TL;DR. I know the feeling.
So when automating infrastructure one of the core infra component is CI/CD. We all know GitLab is a champion in many areas e.g VCS, CI/CD Pipelines to name a few. I was building a Cloud Formation Template for one of the DataOps solutions that my company offers and for that we wanted to automate the Gitlab Installation process as part of the CloudFormation template.
We are using an EC2 Instance where we are provisioning these instances using userData. And GitLab is launched as a docker container.
The challenge for me was to automate the initial root password and generate a…
Introduction: We recently deployed an EKS Cluster for our Streaming App. And we have been using GitLab for quite some time. We were using Ansible roles to deploy our applications in staging and production environments. But we wanted to try something native to Gitlab CI/CD.
1. You have a basic understanding of all technologies included in the title of this article.
2. You have already deployed applications in your Kubernetes cluster as deployment and they are working fine.
3. CI/CD will be triggered only if your commit is tagged with a version number.