Automation Flow to Update Services

Automation Flow to Update Services on Existing Deployed Infrastructure

1. Automated Updates and Upgrades

When a developer pushes the latest updates (e.g., new features, patches, or bug fixes) to the respective branch in the version control system (e.g., Git), it automatically triggers the CI/CD pipeline configured for the customer or MSSP branch.

1. Helm Chart and Docker Image Creation

• As part of the CI/CD process, a new Helm chart is generated, and the application is containerized into Docker images.

• The newly created Docker images are pushed to a central container registry (e.g., Docker Hub, private repository) where all service images are stored and versioned.

1. Webhook Integration with StackStorm

• A StackStorm webhook is integrated into the container registry. Upon successful image creation and push, the webhook triggers a specific StackStorm workflow that initiates the update process.

• The webhook captures essential metadata, such as image version, and passes them as parameters to the workflow.

1. StackStorm Workflow Execution

• The triggered StackStorm workflow fetches the new Docker images and Helm charts from the registry and prepares them for deployment to the Kubernetes cluster.

1. Update Deployment to Kubernetes Cluster

• The StackStorm workflow leverages Helm to update the Kubernetes deployments The update process (rolling upgrade) gradually replaces older versions of the pods with new ones, maintaining service availability.

One more VM needed to automate the deployment process via Stackstorm

Feature	Minimum Specifications Recommended EC2: t2.medium	Recommended Specifications Recommended EC2: m4.xlarge
Operating System (OS)	Ubuntu 20. 04 LTS	Ubuntu 22.04 LTS
CPU	2 CPU Core Processor or equivalent	4 CPU Core Processor or equivalent
Memory	4 GB RAM	16 GB RAM
Storage	20GB	40GB SSD
Network	100+ Mbps	1 Gbps