The recommended approach is to take advantage of configuration management change process in the source code repository. Library/SDK updatesįor mission-critical applications, it's critical that source code and dependencies are updated when new versions become available. Changes to CaC should be deployed via CI/CD pipelines. This practice is known as Configuration as Code (CaC). To combat these outages, configuration for application or infrastructure should be captured as code. Configuration changesĬonfiguration changes are a common cause of application outages. Updates to the infrastructure, such as patching the OS should also be managed via CI/CD pipelines.
All changes to the IaC should be deployed through the CI/CD pipelines. This practice is commonly referred to as Infrastructure as Code (IaC). Infrastructure should be modeled and provisioned as code. Application dependencies, such as runtime environment or packages should be monitored, with updates deployed via CI/CD. The code should be built, linted, and tested against regressions. Application changesĪll changes to the application code should be deployed through CI/CD. The following sections describe changes that should be implemented, where possible, through CI/CD.
The new stamp should be thoroughly tested as part of the release process before traffic is routed to the stamp via a blue/green deployment strategy. For mission-critical workloads, the changes listed below should result in the deployment of an entirely new stamp. CI/CD is the preferred approach to deploy changes to any environment, Dev/Test, production, and others. Application automationĬontinuous Integration and Continuous Deployment (CI/CD) enables the proper deployment and verification of mission-critical workloads. The following sections describe approaches to handling different types of change. Again, maintenance tasks should be automated and manual tasks should be avoided. The technical execution should take advantage of Azure-native platform capabilities, and the use of automated Azure Pipelines to deploy changes to the application, infrastructure, and configuration. It's crucial for the operational success of a mission-critical workload that the end-to-end responsibilities fall within a single team, the DevOps team. Organizational alignment is equally important to operation procedures. This article provides operational guidance for making common changes and updates. All changes and maintenance should be applied using deployment pipelines. The application will evolve over time, keys will expire, patches will be released, and more. Like with any application, change will occur in your mission-critical workloads.
0 kommentar(er)
