GitOps Part 3 - Observability

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.

TensorFlow, Machine Learning and Weave Cloud

This article discusses how InstaDeeps Reinforcement platform can save you time and resources through their visual approach to neural net optimization.

Continuous Delivery the Hard Way

Learn why you need Continuous Delivery and how we evolved Weave Cloud to achieve Continuous Delivery with the tools you already have, like Jenkins, Circle CI and with any container registry like DockerHub, Quay or even with a private registry.

The GitOps Pipeline - Part 2

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.

​GitOps - Operations by 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.

Continuous Delivery vs. Continuous Integration: What's the Difference?

Continuous delivery vs. continuous integration vs. continuous deployment. Do you know what the differences are? Our blog clears it up for you.

Best Practices for Continuous Delivery

Continuous delivery is one of those software development buzzwords that you may have heard before but aren’t really sure what it means to you. As with many buzzwords, however, behind the term is often a great idea that can produce massive...