Kubernetes Continuous Development

Abstract

The scope of this research paper is to develop a continuous integration/continuous development pipeline for microservices application, decide which options will include in our continuous integration phase, utilization of Jenkins to execute blue/green or moving sending, utilizing Ansible or integration/continuous deployment, is the foundation to assemble our “framework”; i.e., Kubernetes Clusters and to make our undertaking stick out, we have actualized checks, for example, security examining, execution testing, joining testing, and so forth! Henceforth, AWS CloudFormation licenses you to exhibit your entire establishment and application resources with either a book record or programming vernaculars. The AWS CloudFormation Registry and CLI simplify it to manage untouchable resources with CloudFormation. This gives a lone wellspring of truth for all of your resources and urges you to standardize system parts used across your affiliation, engaging arrangement consistence, and faster examining. CloudFormation manages choosing the right errands to perform while managing your stack, orchestrating them in the most capable way, and moves back changes normally if botches are recognized. On the consummation of continuous integration, we have set up the continuous deployment which incorporates pushing the constructed Docker container(s) to the Docker storehouse and deploying these Docker container(s) to a little Kubernetes bunch. For our Kubernetes cluster, we have used AWS Kubernetes as a service; to deploy our Kubernetes cluster, we used cloud formation tool on AWS. The languages used for the deployment are PHP and JSON. Preferably, we have been able to run these from within Jenkins as an independent pipeline.