mizu VS helmfile

UP9, Founded 2019, 3,743 stars

API traffic viewer for kubernetes(kinda like wireshark): https://github.com/up9inc/mizu

Mizu – API traffic viewer for Kubernetes\ (4 comments)

Mizu is an open source multi-protocol traffic viewer for Kubernetes that can be used to view API traffic between microservices communicating over synchronous and message queue protocols.​Traffic viewing is essential for troubleshooting bugs, defects, and regressions. It helps developers find the root cause of a problem quicker and therefore deploy faster. Mizu is available to download as an executable binary or as source code directly from its GitHub repository.

As a reminder, Mizu is a lightweight API traffic viewer for Kubernetes that doesn't require any code instrumentation. It provides complete visibility to all API traffic and payloads with support for different protocols and encryption. A short video describing the new feature can be found here [Add link to video].

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