Secure (sensitive) secrets with docker authentication

[ofirgrm]

I'm running Kafka UI on a Docker swarm cluster and would like to avoid specifying sensitive information in the Docker Compose (stack) file or as a Docker environment variable. Instead, I would like to be able to use docker secret. Considering the base scenario of user/pass authentication, I'm expecting a variable, for password, ending with _FILE to which I can assign the location of the docker secret (/run/secrets/password). Even the OAuth2 authentication isn't secure and the client secret will be exposed as an environment variable or as an external file. Either file will eventually find its way to the source control (git) repository with the sensitive information in them (not a security best practice).
Please let me know if there's a way around it, gave it a consideration or planning to correct it in the future?

Thanks.

[Haarolean]

Hi,

1. this repo is no longer maintained, see The future state of UI for Apache Kafka #4255. We've moved to https://github.com/kafbat/kafka-ui
2. I don't quite understand why this should be solved somehow on the app's side and how. There are tools designed for this specifically, like sealed secrets for k8s installation (we have helm charts) and other things, while docker swarm AFAIK is deprecated.

[ofirgrm]

Thanks for the prompt reply.

I'm afraid you've mixed the Docker Swarm 'standalone' (old) version that is deprecated with the integrated version that is very much alive. While you would use k8s for medium to large enterprises, small/medium businesses with small development teams are better off with Docker Swarm which provides a more lightweight and less complex solution.

The app should provide a way to read sensitive data/file from a custom location. I would love to expand on this topic, but would you rather I use the new project location instead?

[Haarolean]

but would you rather I use the new project location instead?

yes please. Or feel free to jump on discord (the link is available in readme) for a quicker discussion :)