pluto
helmfile
Our great sponsors
pluto | helmfile | |
---|---|---|
17 | 39 | |
1,943 | 4,020 | |
3.7% | - | |
6.3 | 0.0 | |
27 days ago | 11 months 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.
pluto
- Updating from 1.25.15 to 1.26.10
-
How do you handle continuous k8s cluster version upgrades in your organization?
You have to constantly run tools like https://github.com/doitintl/kube-no-trouble / https://github.com/FairwindsOps/pluto.
- How do you guys monitor K8s core services new versions
-
eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat
You might like https://github.com/FairwindsOps/pluto
- Kubernetes upgrade
-
kubernetes provider resources v1 vs non-v1 is it just me or is this dumb?
I knew it was unsupported so about 6 months ago I had started an effort to switch to Kyverno, which is far better and actually supported. The version of Kyverno I was using had a v1beta1 AdmissionController. Fortunately that was in a helm chart so easily caught by pluto before my upgrade.
-
Helm chart - fluent-bit
If you're looking for API deprecations specifically you can look into pluto from fairwinds.
-
Updating EKS to 1.22: dealing with deprecated APIs on ALB Ingresses
you can use https://github.com/FairwindsOps/pluto to check for api deprecations before updating the cluster.
-
How do you keep up to date with Kubernetes versionning?
Pluto can help determine if you're using deprecated APIs, which is a source of continuous hassle: https://github.com/FairwindsOps/pluto
-
Detecting Kubernetes API Deprecations with pluto
In large clusters with dozens of resource types and versions, this can become tedious and error-prone. Luckily, there are tools like pluto by FairwindOps which assist us in spotting deprecated and soon-to-be-removed resource API versions.
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 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.
-
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
-
Interesting tools?
helmfile is not widely known but awesomeme
-
How to keep track of 3d party applications helm chart on K8S?
Not exactly an answer to your question, but we have created a separate project called "cluster" where we define all cluster dependencies via https://github.com/roboll/helmfile, meaning that you always know what (+versions) you have in the cluster and can easily reproduce it. It does not solve an issue with knowing what project has a new version now but at least you can be sure what version is in your cluster
-
Requesting guidance. Helm deployment and structure.
Dont.Use.Umbrella.Charts. If you need to deploy multiple things at once, but you dont wanna deal with relative complexity of Flux or ArgoCD - use helmfile. https://github.com/roboll/helmfile
What are some alternatives?
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
helmsman - Helm Charts as Code
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.
helm - The Kubernetes Package Manager
argocd-image-updater - Automatic container image update for Argo CD
terraform-provider-flux - Terraform provider for bootstrapping Flux
helmwave - New 🌊 wave for @helm
kube-no-trouble - Easily check your clusters for use of deprecated APIs
rancher - Complete container management platform