You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using standalone, it would be helpful to set the root password to something other than default using an environment value and/or config. like MILVUS_ROOT_PASSWORD. This would enable the standalone container to start in a more secure manner and configurable, rather than having to start a Milvus instance, then have a separate client use the default admin password, and update itself. Saving a step.
Why is this needed?
The default password for root is well documented. Not having a way to change this in config for startup of the standalone leaves an opening for even authenticated commands to just guess at the default (it's the equivalent of admin/admin). Other containers I've worked with enable setting the root password as a configurable aspect in environment variables so that it is secure at startup.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What would you like to be added?
When using standalone, it would be helpful to set the root password to something other than default using an environment value and/or config. like MILVUS_ROOT_PASSWORD. This would enable the standalone container to start in a more secure manner and configurable, rather than having to start a Milvus instance, then have a separate client use the default admin password, and update itself. Saving a step.
Why is this needed?
The default password for root is well documented. Not having a way to change this in config for startup of the standalone leaves an opening for even authenticated commands to just guess at the default (it's the equivalent of admin/admin). Other containers I've worked with enable setting the root password as a configurable aspect in environment variables so that it is secure at startup.
Anything else?
No response
The text was updated successfully, but these errors were encountered: