While Helm helps with getting applications running, you need other tooling to keep them up to date when something changes. Check out our alpha release of our Helm integration in Weave Flux. It makes sure your Helm chart releases are kept up to date with what’s in Git. You can try it out using the published repository in Github.
Looking at a CICD pipeline with security in mind, reveals some interesting concerns. Consider the credentials and access typically assigned to each step, and what’s actually required for each step - Read Write access, and Read Only access. The CI system can be a target, because it’s got credentials for the source code, the image repo and the cluster, and it crosses two logical security boundaries. Learn how you can mitigate this with a GitOps approach.
Discover how to achieve an automated continuous delivery with Kubernetes, Google Cloud Platform and Weave Cloud multiple time a day. Discover the role, observability and metric monitoring play for determining whether you’re progressing once you’ve increased your speed of deployment.
This blog post explains techniques for development teams who strive for high velocity continuous delivery using Kubernetes and Docker. When we say “high velocity” we mean that every product team can safely ship updates many times a day — deploy instantly, observe the results in real time, and use this feedback to roll forward or back. The goal is for product teams to use continuous experimentation to improve the customer experience as fast as possible.
A “you build it, you own it” development process requires tools that developers know and understand. “GitOps” is our name for how we describe modern best practices for high velocity application development with cloud native tools. Read this summary post about the GitOps pipeline model, why its beneficial to adopt this methodology and how to get started.
Observability can be seen as part of the Continuous Delivery cycle for Kubernetes. Observed state must be compared with the desired state in Git. The role of a GitOps dashboard is to enable observation and speed up understanding and validation of the system, and suggest mitigating actions. Monitoring alone does not answer all questions: metrics are symptoms but not the disease.
GitOps relies on your whole system to be expressed declaratively. The GitOps pipeline model places Git at the design centre - everything upstream of deployment is anchored by Git. As a result a developer can update some code in GitHub and release into production as a pull request.
Alexis Richardson is defining “GitOps” as a methodology for developer tooling to drive operations. This post discussed the use of declarative tools and best practices of configurations being code and therefore should be versions controlled.