Devtron is an open-source software delivery workflow for Kubernetes. It combines CI, CD, and GitOps principles and processes through Argo CD, Argo Workflows, Argo Rollouts, Clair, and quite a few other tools.
Application lifecycle typically consists of three parts. First, we develop locally, we deploy to temporary environments, usually due to creating pull requests, and we proceed towards a permanent environment, all the way until production. Can we streamline and simplify the whole application lifecycle process by combining Kubernetes, vCluster, DevSpace, Argo CD, k3d, and GitHub Actions? Even if you prefer a different combination, the principles behind this process can be easily applied to a myriad of other tools.
Tekton is a powerful and flexible open-source framework for creating CI/CD systems aiming at becoming a de-facto standard for running pipelines and workflows in Kubernetes. It allows developers to build, test, and deploy across cloud providers and on-premise systems.
What is GitHub actions? How to use GitHub Actions, and does it work? How can we leverage its marketplace, and what is the pricing? Is it a good solution for CI/CD pipelines? Let’s answer those and other questions through tutorial and review.
Since the increase in popularity of continuous delivery (CD), there was an increase in the number of tools marketed as CD solutions. That’s normal. It is only natural for software vendors to ride the waves. They need to sell, and there’s nothing better to sell than whatever is popular at a given moment. Continuous delivery is one of those "popular" waves.
On the surface, there is nothing wrong with buying tools that solve problems. You have a problem, a vendor has a solution, you buy it, they earn money, and you have a good return on investment. Everybody wins, except when the tool does not do what it’s supposed to do. That’s when we run into issues.