hub VS keptn

Let's now install a helm chart from an opensource oci repository (ref: https://artifacthub.io/); Just for an example we will install nginx chart.

Helm charts are stored in a chart repository. This repository analogy is similar to docker hub where you can pull or push images. In a chart repository, you can also pull your charts from the repository and update the repository locally for you to use the chart. The repository that hosts Helm charts is ArtifactHub. ArtifactHub is a web based application that enables finding, installing and publishing Kubernetes packages and configurations. Searching for the helm charts can be done in two ways:

When you're on the lookout for readily deployable and customizable applications to integrate into your cluster, your ideal destination is ArtifactHub. This centralized platform serves as a comprehensive resource, gathering an array of public Helm Chart links for your convenience.

Helm has an official Helm Chart repository called ArtifactHub where developers can push and publish their Helm Charts. In this repository, you can easily find Helm charts for any Kubernetes application and reuse them. For complex applications like Jenkins, it is best to use the official Jenkins Helm Chart. Many Developers have contributed to the Jenkins Helm chart and it has all the Kubernetes YAML files. It will save us time in creating our custom Jenkins Helm chart. In this tutorial will search and download the official Jenkins Helm Chart from ArtifactHub. We will then install the official Jenkins Helm Chart on the Kubernetes Cluster using Helm. Let's install Helm.

The next time you want to search for public Helm Charts, I recommend first searching through Artifact Hub (sort by Stars).

You can also add the artifacthub repo file, to claim ownership, it's optional though.

One of the other places I spent a lot of time at at KubeCon NA was the CNCF Project Pavillion. I was very happy to see that it was a bit larger than the area we had during KubeCon EU, but I still wish that it was bigger and wasn’t so tucked away in the corner. A number of booths were showcasing their projects with demos through the week, hosted Q&A time, and gave away swag. If you are still trying to understand the Cloud Native Ecosystem, you can look at this very extensive map of the landscape and projects under the CNCF, some of which are more advanced than others. Of course I’m biased, but I’m really excited for the work that Keptn is doing in helping developers have more control over their application lifecycle. I’m also very excited to see where Backstage goes and how other CNCF projects can integrate with their service catalog.

I can’t speak from experience, but I think Keptn might be worth looking into: https://keptn.sh/

Go try this out and share your feedback on what you like about this integration and what you’d like improved. Feel free to create issues, engage in discussions on the Keptn Slack and Litmus Github repository. Stay tuned for more updates on how you can leverage Keptn & LitmusChaos CNCF projects to build and ship resilient cloud-native applications!

If you want, you can also manually download the binary file from Github and install the CLI by moving it into your path.