kubespy
helmfile
kubespy | helmfile | |
---|---|---|
10 | 39 | |
2,830 | 4,024 | |
0.8% | - | |
5.4 | 0.0 | |
17 days 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.
kubespy
-
How I get better feedback on my PRs (and how you can, too)
lang="en"> charset="utf-8"> Hello, world! Hello, world! 👋 Deployed with 💜 by new href="https://pulumi.com/">Pulumi.
-
AWS EC2 Auto Scaling, Target Tracking Policies and Prometheus Exporters
Pulumi IaC will help us bring up our infrastructure on the AWS Cloud. Check out pulumi.com if you still need to become familiar with it. You can deploy this demo stack using the Pulumi button below.
-
Terraform - How do you handle secrets?
There are other infrastructure as code tools that take secrets seriously. Pulumi encrypts all values in state and you can even bring your own key from your cloud provider
-
Observability Mythbusters: Yes, Observability-Landscape-as-Code is a Thing
*Codifying the deployment of the OTel Collector *(to Nomad, Kubernetes, or a VM) using tools such as Terraform, Pulumi, or Ansible. The Collector funnels your OTel data to your Observability back-end. ✅
-
Interesting tools?
KubeSpy - to see what's going on a deployment real time. https://github.com/pulumi/kubespy
-
My "infrastructure as code" tool to manage production-grade clusters
it takes too much time, terraform configs are not easy to use also. Pulumi is much better to maintenance. Cloudy is good enough for launching a production-ready cluster in 5-10 minutes. It could be an alternative to kops
-
We're building an open-source tool to deploy infrastructure in multiple clouds
Just wanted to mention a Terraform alternative I really like, especially cause it's infrastructure as code (IaC) http://pulumi.com/, though I'm not sure about their approach on multi cloud, haven't used it in quite a while
-
Deploying Kubernetes Clusters in Increasingly absurd languages
That is the entire point of Pulumi, you should give it a try
-
Tips: Conditional Expression on Terraform
pulumi.com if you are interested in doing anything dynamic inside of your templates (i.e. conditions) take a look at pulumi
- Ways to to trigger terraform modules
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?
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
kops - Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
kured - Kubernetes Reboot Daemon
helmsman - Helm Charts as Code
nginx-prometheus-exporter - NGINX Prometheus Exporter for NGINX and NGINX Plus
kustomize - Customization of kubernetes YAML configurations
google-cloud-cpp - C++ Client Libraries for Google Cloud Services
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
multy - Multy - Easily deploy multi cloud infrastructure. Write cloud-agnostic config deployed across multiple clouds
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.