DevOps, cloud, CI/CD articles

Build and Deploy Docker Images to Oracle Cloud Infrastructure Container Engine for Kubernetes(OKE) using CircleCI With the growing adoption of the micro-services architecture, modern day applications are being developed as micro-services with the ability to scale the individual services independently. This loose-coupling provides the power for developer to make changes to the individual components and push the changes to production independently. When it comes to underlying infrastructure to deploy the micro-services, docker containers are most popular. At the enterprise level we need container management and orchestration solution to manage these containers. Kubernetes is the front-runner in this space since the time when it became open-source. Almost all the cloud providers are providing the kubernetes service in their cloud now. Container Engine for Kubernetes(generally referred as OKE) provides the production-grade container solution for Kubernetes with the highly predict

Terraform — Infrastructure as Code There are many tools available for the configuration management in the software industry. Ansible, chef, puppet, salt to name a few popular ones. But when it comes to infrastructure management there are a few tools like Terraform, cloud formation [from AWS], ansible.  Why Terraform ? Infrastructure provisioning is the first step in any organization’s application delivery process, because without the infrastructure we will not be able to deploy the applications. Due to the adoption of the DevOps and agile development methodologies, automation is the de facto in every stage of the software development life cycle. Having said that, writing infrastructure as code has become the standard for storing the infrastructure configuration and versioning the same. Terraform has become very popular tool in this space due to its simplicity and the support it has for verity of cloud providers.  What is Terraform? As quoted in the official website https:

Infrastructure setup is usually done by creating new instance, pre-configure it with the dependencies and then deploy the application. As the time goes by, new versions of the application would be deployed, many configuration changes would be done by administrators either through automation or many times through manually ssh into the server which may not have any record in version control systems. This makes the server unpredictable for the future deployments and may fail. This type of constantly updating the infrastructure as and when required is called mutable infrastructure. On the other hand there is something called immutable infrastructure where once the application is bundled with the pre-configured custom image and an instance gets created, nothing can be changed on the instance thereafter. If there is any new changes needs to be done to the application or the configuration of the server, then new image gets created from base image. This replaces the old instance and same p