helmfile
LocalStack
Our great sponsors
helmfile | LocalStack | |
---|---|---|
39 | 154 | |
4,024 | 52,145 | |
- | 1.3% | |
0.0 | 9.9 | |
about 1 year ago | 4 days ago | |
Go | Python | |
MIT License | GNU General Public License v3.0 or later |
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.
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
LocalStack
- LocalStack – a functional local AWS cloud stack
-
Let's build a screenshot API
Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:
-
LocalStack e AWS CLI: Como desenvolver localmente com a AWS
Acesse o site da LocalStack e faça login.
-
Cutting down AWS cost by $150k per year simply by shutting things off
To give this a slightly different spin:
--> "The best optimization is simply not spinning things up."
At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.
We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".
What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.
-
Getting Amazonka S3 to work with localstack
(For others who hadn't heard of it: localstack is
- LocalStack v3.0.0
- Localstack, a "AWS" local para desenvolvimento em cloud
-
Integration tests with AWS S3 buckets using Localstack and Testcontainers
LocalStack Website
- LocalStack: A functional local AWS cloud stack
-
Simulando a AWS no seu ambiente Local
O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.
What are some alternatives?
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
sst - Build modern full-stack applications on AWS
helmsman - Helm Charts as Code
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
kustomize - Customization of kubernetes YAML configurations
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
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.
Appwrite - Build like a team of hundreds_