Cloud Native Application Delivery Flashcards
Popular CI/CD tools
CircleCI
Jenkins
GitLab
Spinnaker
Jenkins X
Tekton CD
ArgoCD
GitOps
Storing not only code in the git but also
configuration
network
policies
infrastructure
GitOps frameworks using pull-based approach
Flux
ArgoCD
Push-based CI/CD
Changes triggered by commit or merge request
Pull-based CI/CD
Agent watches the repository and compares state of repository to actual running state. If difference is detected the agent applies the changes to the infrastructure.
How is ArgoCD implemented
as an Kubernetes controller
Flux is built with
GitOps Toolkit
Inner working of Kubernetes is closer to Pull-based or Push-based CI/CD?
Pull-based
Why is Kubernetes particularly well suited for GitOps?
Because it provides an API and is designed for declarative provisioning and changes of resources
Why Kubernetes inner workings is similar to Pull-based approach?
A database is watched for changes and the changes are applied to the running state if it doesn’t match the desired state.