Conveyor CI / CD DevOps with Azure AKS
The microservices are now one of the trends in web applications architectures and platforms. Architecture based on microservices are a number of advantages compared to a monolithic architecture. Thanks to Microsoft Azure DevOps conveyors are among the most simple to set up pipelines of CI/CD for the release of new builds for AKS services.
A Kubernetes cluster is a very important system orchestration containerization in the industry. The solution that Microsoft suggested for creating microservices using Kubernetes called the Azure Kubernetes Service or AKS.
The Benefits Of Kubernetes:
• Deploy applications quickly and predictably, and also the easy coordination of system deployment.
• Restriction of connections between containers.
• Continuous monitoring and management of containers.
• Increased reliability and availability.
• Application scaling to handle load changes on the fly as needed.
• Best use of resources.
So why use Azure solutions AKS?
• Placement of your Kubernetes environment.
• Easy integration with Azure services, such as load balancing, storage, Azure blobs, Azure Active Directory, application gateway, traffic Manager, Azure, etc.
• Quick and easy deployment.
• Simple and safe management of container applications.
• Continuous integration through the adoption of the concept of Azure Pipeline to create a Docker image for faster deployment and reliability.
• Creation of resources and infrastructure within the Azure Kubernetes cluster using manifest files, deployments and services.
• Service management of AKS is available free of charge to Microsoft Azure.
Next I would like to consider a phased deployment strategy AKS:
1. The developer submits the source code to the repository to Azure.
2. Azure pipeline starts to build by cloning the application code from the repository in Azure or build agent is hosted on a Microsoft server or in a self-governing agents of the Assembly.
3. Agents build Azure will build the job and generate deployable artifacts that can be sent to the location in the staging directory artifacts.
4. Azure pipeline creates a Docker image with the artifacts of the application code, mark the image, and sends it to the registry container Azure.
5. Azure pipeline annotates the application code that was placed in the container, and sends the code to the repository to Azure.
6. Azure pipeline executes commands from kubectl to redeploy modules.
The process of redeploying starts with extracting the last image from the list of Azure containers.
7. The deployment process of Azure Kubernetes:
• ConfigMap storage insensitive environment variables.
• The secrets of storing sensitive environment variables.
• Constant volume, storage blobs, etc.
• Azure key vault to store secrets DevOps, service accounts, and managing certificates TLS/SSL.
• Managed Azure.
8. Creating objects Kubernetes (services, object Ingress, etc.) to communicate with the pod.
9. Configuring the load balancer, forwarding rules and the appointment of an external public IP address (the controller of the incoming traffic).
10. Users access the application with a public URL.
Journal: Journal IT-Expert [No. 10/2020], Subscription to magazines