CloudGraph cli VS helmfile

Looks similar to https://github.com/cloudgraphdev/cli

Honestly, half baked and not very useful at all. If you want an actual single GraphQL based API for ALL of your AWS services, plus CSPM (CIS 1.2, 1.3, 1.4, PCI, and NIST) check out https://github.com/cloudgraphdev/cli. Completely free OSS

https://github.com/cloudgraphdev/cli the GraphQL API for K8s, AWS, GCP, and Azure

Check out https://github.com/cloudgraphdev/cli. It supports a vast majority of AWS services and creates a type-safe GraphQL definition of your entire account

If you are looking for a type-safe asset inventory of your GCP footprint(s) you can check out https://github.com/cloudgraphdev/cli. Along with the asset inventory (which you can query via GraphQL) it will also check for CIS 1.2 compliance failures.

CloudGraph can give you a type-safe asset inventory (plus CIS 1.2 compliance checks) for all of your resources on GCP: https://github.com/cloudgraphdev/cli

Some great suggestions here. I would also suggest running some tool like: https://github.com/cloudgraphdev/cli with the AWS CIS policy pack so you can ensure you are following best practices.

You can use a tool like [CloudGraph](https://github.com/cloudgraphdev/cli) to do this pretty easily.

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.

Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.

Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”

To make managing the Helm deployments a little easier I used helmfile (https://github.com/roboll/helmfile).

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 )

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

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.

helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile

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.

Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile