helm VS crossplane

Within the architecture of Cyclops, a central component is the Helm engine, which allows the dynamic generation of configurations. This engine serves as a key mechanism for efficiently managing settings and parameters in the Cyclops framework.

I know naming things is hard, but Helm has been in use as a tool in the Kubernetes ecosystem for years now.

https://helm.sh/

Helm is a widely used package manager for Kubernetes, designed to simplify and automate the deployment, scaling, and management of applications. It provides an efficient way to define, install, and upgrade even complex Kubernetes applications.

The choice of a winner depends on the specific requirements, priorities, and constraints of the organization or system you're working with. Sigstore is well-suited for organizations prioritizing secure and transparent software updates for various artifacts, including Helm charts, alongside images. It has great community support and features, such as interoperability between registries, making it a great choice for most organizations. Moreover, most container registries support the signing format.

The first thing we need to do is decide on how we want to package and manage Kubernetes manifests for different environments. There's a tool called Helm which @StevenMurawski covered here, and another tool called Kustomize which I personally like to use. Both tools are great for packaging and managing Kubernetes manifests and also supported by FluxCD, but I prefer Kustomize because it is pretty easy to use and built into kubectl.

Helm Dashboard is an open-source project by Komodor that offers a visual and user-friendly way to manage and visualize all the Helm charts installed in your clusters. Instead of using the terminal, you can leverage the Helm Dashboard's intuitive UI to perform a variety of tasks that make working with Helm a breeze. Here are some of its key features:

Next, we will install APIClarity using Helm.

Helm is a package manager for Kubernetes. Helm is an open-source project originally created by DeisLabs and donated to the Cloud Native Foundation (CNCF). The CNCF now maintains and has graduated the project. This means that it is mature and not just a fad.

For CLI utilities written in Go, Cobra is the go-to command line wrapper, used by the likes of Kubernetes, Github CLI, Helm, and many more.

did anyone adopt in production https://crossplane.io ?

- https://github.com/crossplane/crossplane/blob/master/design/one-pager-composition-environment.md

In the overall scheme of things , look at services like backstage.io , crossplane.io and opslevel.com to get ideas. This is not necessarily an endorsement of the services. If all you want is to handle cloud resources and that's it, Terraform can be enough with what ever flavor of web technologies you and your team are comfortable with and can support it along the way. Doesn't take much to create a js based website to collect data from a form, or use other means to collecting data as long as its recorded and transparent for accountability.

Practically, you'll be replacing stock k8s resources (deployments) with custom ones like Argo Rollouts with Keda autoscaling, so you have to plan the respective Gitops CD pipeline (fluxcd/argocd with some crossplane), as well.

assess https://crossplane.io/

Also, 5 cents * assess https://crossplane.io/ * dont use terraform, ansible or other stone age stuff in k8s * dont call fluxcd or argo gitops, those 2 companies are just exploiting the practice name.

Crossplane [1] is great way to create and manage resources across cloud providers, MSPs via kubernetes objects.

[1] https://crossplane.io