ketch
helmfile
ketch | helmfile | |
---|---|---|
27 | 39 | |
654 | 4,024 | |
0.2% | - | |
6.8 | 0.0 | |
3 months ago | about 1 year ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ketch
-
Acorn: A lightweight PaaS for Kubernertes, from Rancher founders
Here at Suse we looked at https://github.com/theketchio/ketch and the founder for Acorn did some diligence there. Is it a copy?
-
Helm is both "package manager" and "templating engine" - probably the best package manager but horrible template engine
An idea may be to look at something like Ketch, and potentially combine it with Pulumi, TF, or others. Here is an example
-
A simple application deployment framework for Kubernetes!!
You have some more “established” tools, such as Ketch but from what I’ve seen, many people are building it in house by using tools such as Helm, Crossplane, or others
-
Application deployment framework.
Pretty much what Ketch has been doing for a while already, and Ketch is part of a larger app platform
-
Acorn - the new cool kid for app deployment to Kubernetes
Pretty much what Ketch has been doing for a while now
-
Automatic generation of Manifest files.
Another option you have is to use open source projects like Ketch that can make this process more "developer friendly". Here is an example
-
Deploying Python apps on Kubernetes without complexities
Because of that, we have created an open-source project called Ketch to make life easier when deploying apps on K8s.
-
Nodejs App From Code To Kubernetes Cluster
The team is excited about enabling developers to focus on their application code instead of infrastructure. We would love it if you could show your support by starring the project on GitHub and sharing this article with your teammates.
-
Stronger abstraction for deployments
It might be worth having a look at the open source project Ketch
-
Deploying applications on Kubernetes using TypeScript
Instead, by combining the application-focused approach from Ketch with the IaC model from Pulumi, developers can have an application-focused layer they can leverage to quickly deploy their applications without getting into the underlying infrastructure details exposed by Kubernetes.
helmfile
-
Deploy IRIS Application to Azure Using CircleCI
What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.
-
[2022] [Updated] Alternative to Helmfile
Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.
-
Projectsveltos: Manage Kubernetes addons in multiple clusters
Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”
-
How are you handling ILM on kubernetes?
To make managing the Helm deployments a little easier I used helmfile (https://github.com/roboll/helmfile).
-
Helm Charts Microservices
But in general it's always easier to keep things quite separated. Meaning in separate helm releases. If you want to be able to manage things "together" at will, then you can use helmfile ( https://github.com/roboll/helmfile )
-
How to Build Software Like an SRE
I agree; helm is too declarative.
Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.
0 - https://github.com/roboll/helmfile
-
helmfile sync vs helmfile apply
I went through the Helmfile repo Readme to figure out the difference between helmfile sync and helmfile apply. It seems like unlike the apply command, the sync command doesn't do a diff and helm upgrades the hell out of all releases 😃. But from the word sync, you'd expect the command to apply those releases that have been changed. There is also mention of the potential application of helmfile apply to periodically syncing of releases. Why not use helmfile sync for this purpose? Overall, the difference didn't become crystal clear, and I though there could probably be more to it. So, I'm asking.
-
Managing multiple repos
helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile
-
Helm is both "package manager" and "templating engine" - probably the best package manager but horrible template engine
I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.
-
So I've installed grafana, loki, and prometheus on the personal Kubernetes cluster via Terraform. Now what?
Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile
What are some alternatives?
kubevela - The Modern Application Platform.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
helm - The Kubernetes Package Manager
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
porter - Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.
helmsman - Helm Charts as Code
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
kustomize - Customization of kubernetes YAML configurations
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.