So, given these shenanigans, the reason to consider #EnvKey over #Infisical is that EnvKey is, on-paper, fully FOSS where Infisical is "open core". But Infisical has no problem with you shipping their "community" version with a helm chart. They even provide one!

https://infisical.com/docs/self-hosting/deployment-options/kubernetes-helm

I'm all for adopting a FOSS project that *almost* meets my needs and making it better until it does, but seeing EnvKey do some apparent self-sabotage really turns me off from wanting to contribute to it.

I'm starting to wonder if this is intentional to make it harder or impossible to do this with helm, since the "community" version of this fully open source project has a hard-coded disable for upgrades, and well, having a helm chart provides an upgrade path for something that #EnvKey seems to be attempting to paywall.

This unfortunately has the opposite effect than they are probably wishing it has, in that I'm less likely to continue to want use the paid EnvKey, or EnvKey at all.

But why?

Trying to decide if I want to commit to writing and publishing a #helm chart for the #EnvKey API server. #Kubernetes

Can it be, a promising truly #opensource #Hashicorp #Vault alternative? You can pay for hosting or on-prem support, but the stack appears to be fully FOSS and includes a webUI! #envkey

https://envkey.com/