kamus VS webui

I tried using the idea at https://stackoverflow.com/questions/54190837/helm-install-in-kuberneres-error-this-command-needs-2-arguments-release-name but it didn't help. Can you spot what I am doing wrong? Thank you.

Kamus may represent a compromise between Sealed Secrets and SOPS. It was created especially for the GitOps use case and includes an operator. It can either manage the key material itself or obtain it from the KMS of the cloud providers. Another special feature is that Kamus encrypts secrets directly for an application. They are then decrypted by the application itself or by an init container. This means that the unencrypted secret is never present on the API server and ideally also not in an environment variable with in the container.

There is no UI for Flux. It does have an experimental UI that is not in an active development state at the time of writing this.

This allows the developer to analyze their deployments and correct errors all without having to access the cluster. For authentication , there are interfaces for common protocols, such as LDAP and OIDC. Via configurable roles and groups, users can granted access the projects and applications for which they are responsible. The developers of Flux v2 are currently working on a web interface. However, it is still in an experimental state.

That's what I said: "I'm a Flux guy." I agree that Flux v2 is much better than Flux v1. But setting up ArgoCD is a drag. With Flux, you just run the CLI command and everything is committed to the repo and deployed in the cluster. Flux is only missing the UI but I think that this will change soon (https://github.com/fluxcd/webui).