dumb-downloader
helmfile
dumb-downloader | helmfile | |
---|---|---|
1 | 25 | |
0 | 3,349 | |
- | 5.5% | |
4.3 | 9.6 | |
4 months ago | 4 days ago | |
Rust | Go | |
MIT License | 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.
dumb-downloader
-
Download packages for different architectures in your Dockerfiles using dumb-downloader, instead of writing scripts or separate Dockerfiles
Link: https://github.com/allanger/dumb-downloader
helmfile
-
Taming FluxCD HelmReleases: The Kustomize Way approach
The answer lies in a simple yet powerful sub-command – helm template (or helmfile template if you use Helmfile). This command allows you to locally render helm charts along with your desired values, generating the final deployment manifest files.
-
Installing multiple helm charts in one go [Approach 2 - using helmfile]
sudo wget https://github.com/helmfile/helmfile/releases/download/v0.159.0/helmfile_0.159.0_linux_amd64.tar.gz sudo tar -xxf helmfile_0.159.0_linux_amd64.tar.gz sudo rm helmfile_0.159.0_linux_amd64.tar.gz sudo mv helmfile /usr/local/bin/
-
Simplified Deployment: A Deep Dive into Containerization and Helm
Installation: https://github.com/helmfile/helmfile/releases
-
Helm-Compose – The Docker-compose like tool for K8s development
What are the benefits over using helmfile? https://helmfile.readthedocs.io/
-
self-built apps: do you like using helm or kustomize to deliver them to kubernetes
Helm charts and Helmfile
-
Download packages for different architectures in your Dockerfiles using dumb-downloader, instead of writing scripts or separate Dockerfiles
And now I can just run dudo -l "https://github.com/helmfile/helmfile/releases/download/v{{ version }}/helmfile_{{ version }}_{{ os }}_{{ arch }}.tar.gz" -i /tmp/helmfile.tar.gz -p $HELMFILE_VERSION
-
Declarative GitOps for...my ArgoCD itself?
I might be misunderstanding your question but we use https://github.com/helmfile/helmfile along with Argo, so essentially between eks and those I could rebuild our entire cluster in minutes.
- Docker helm
-
Which GitOps for very small teams?
I am asking which do you choose, Flux or Helmfile. edit: and what criteria do you use to select.
-
In a gitops world, what does your team do to reduce cycle time for devs?
do you publish your own helm chart for your internal services and use it in every environment? if so, you could try to use helmfile within the service's repo itself and store values in a helm/$env directory. then enhance your ci to deploy to dev after the merge/image build phase directly. to try and cut out what sounds like a "deployment/config repo" step you have in the middle that's making everything a pain.
What are some alternatives?
bitwarden_rs - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
vals - Helm-like configuration values loader with support for various sources
libreddit - Private front-end for Reddit
helmwave - New 🌊 wave for @helm
RustScan - 🤖 The Modern Port Scanner 🤖
helmsman - Helm Charts as Code
vaultwarden - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
kpt - Automate Kubernetes Configuration Editing
youki - A container runtime written in Rust
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
zarf - DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev/
library-charts - ⚠️ Deprecated : Helm library charts for the k8s@home Helm charts