I don't think those are mutually exclusive options :) Most developers, especially with lots of legacy apps are better off using a secrets manager. But there is no reason to not push the boundaries of security for new software and onboard passwordless and secretless options.
P.S.
I tried Infisical a couple of months ago. I think if I was Hashicorp Vault team's PM, I'd be worried. Your team has done such a great job at U.X. I was astonished to see an early startup with such a great integration catalog. I think you aced it - modern developers are desperate for out of the box integrations with 100+ services they have to use every day.
No problem! Keep it up with out of the box integrations, focus on U.X. and developer experience and I think you will be on track to become as big or bigger than Hashicorp :)
The Kubernetes integration allows you to periodically fetch secrets from an Infisical project and save them to a native Kubernetes secret. You simply specify the service token that should be used to retrieve the secrets from infisical and the operator handles the rest. Read more about it here! https://infisical.com/docs/integrations/platforms/kubernetes
It really depends on how you set it up. If you prefer, you can choose to split non-sensitive environment variables and sensitive secrets into different projects - and use them for different purposes / in different ways.
It very much sounds like security is an after thought.
Seems cool if you need to sync env vars, but you should probably just be using battle tested etcd+confd or console+console template.
This product seems to be based on some incredibly misguided principles (from a security perspective). I don’t think a technology like this has any place in a modern enterprise.
Part of the whole point of using a secret manager is to avoid storing them in environment variables.
That coupled with the lack of an API and the use of MongoDB are just too many red flags for me to ignore.
