what happens in the system ● Code changes always go through an automated process ● Deployments, tests, and rollbacks controlled through Git flow ● Integration with secrets providers ● No hand-rolled already there. This means that tasks such as… ● Compiling code ● Running unit/integration tests ● Security scanning ● Static analysis ...are not a concern of GitOps tools and are assumed that you want to run some smoke tests AFTER a deployment has finished and the result of the tests will decide if a rollback will take place or not. Smoke tests As I said in the previous

in your cluster. When you push that code to Git, the continuous integration tool kicks off unit tests that eventually build the Docker image that gets pushed to the container registry. With a typical DELIVERY PIPELINE CONTINUOUS INTEGRATION CONTINUOUS DEPLOYMENT Write Code VCS Code Base Unit Tests Integ Tests Container Registry DEPLOY eBook 8 Security and the Typical CI/CD Pipeline How secure is the revised, it is merged to Git. 3. The Git merge triggers the CI pipeline that runs a series of tests, builds a new image and pushes the new image to a container registry. 4. Weave Cloud’s Deployment

continuous stream of releases. Figure 1-1: The CI/CD workflow. Continuous integration builds and tests new code changes and merges them into a shared repository on a regular basis. CI is a form of rapid delivery one step further, deploying the changes into actual production (after they pass automated tests). Continuous deploy- ment supersedes continuous delivery and is now seen as full DevOps automation commit to a specific repository or branch can trig- ger a pipeline that builds the application, runs tests against it, and maybe triggers other pipelines. The key point here is that the process is synchronous

├── ingress.yaml │ ├── NOTES.txt │ ├── serviceaccount.yaml │ ├── service.yaml │ └── tests │ └── test-connection.yaml └── values.yaml #Required ``` KUSTOMIZE cluster. When the developer pushes the code to Git, a continuous integration tool kicks off unit tests that eventually build the Docker container image that gets pushed to the container registry. re-approved, it is merged to Git. 4. The Git merge triggers the CI and build pipeline, runs a series of tests, and then eventually builds a new image and deposits the new image to a registry. 5. The Deployment

Consistent Post-Test update of image reference Con Image reference updated in git before integration tests, manage rollback? Inconsistent Con Pipeline tools must be able to wait for sync Application repo