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
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
It's not supported by the operator for now, and the future support should be added.
It's still being discussed whether attu should be considered as component of milvus instance. Maybe we should make it an option for to be installed together with the milvus-operator, since only one attu is needed in order to manage all the milvus instances in the whole kubernetes cluster.
What do you think of this?
If there's a discussion about whether it should be a component of a milvus instance I wouldn't open it here as well :)
but for now, yes, mainly because when installing a cluster today using the charts it is an option.
I'm not sure if Attu is supported or not by the operator.
if it is, it would be great if it could be added to the docs (docs/CRD maybe..)
if not, it would be lovely to add support to it, like I can deploy the Milvus helm chart with env variable like this:
it would be great if we can set it under the components part of the yaml file
The text was updated successfully, but these errors were encountered: