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
Hi there,
I got some issuese when I was going to install milvus standalone, but sine it's from minio, therefore not really sure here is the proper place to ask.
When I tried to install milvus standalone version with helm chart, I got the issue, here is my values.yaml setup. (For minio part)
minio:
enabled: truemode: standalone
And I got an error in k8s side,
Pods "milvus-standalone-minio-74d96b99f9-" is forbidden: error looking up service account default/milvus-standalone-minio: serviceaccount "milvus-standalone-minio" not found:Deployment does not have minimum availability.
Seems like system tried to install minio in default namespace, however, I was using milvus namespace. And the service account had been installed into milvus namespace.
And I looked into the source code of the helm chart (minio part)
helm chart version: 8.0.17
Hi there,
I got some issuese when I was going to install milvus standalone, but sine it's from
minio
, therefore not really sure here is the proper place to ask.When I tried to install milvus standalone version with helm chart, I got the issue, here is my
values.yaml
setup. (For minio part)And I got an error in k8s side,
Seems like system tried to install
minio
indefault
namespace, however, I was usingmilvus
namespace. And the service account had been installed intomilvus
namespace.And I looked into the source code of the helm chart (minio part)
helm chart version:
8.0.17
Looks like there's NO setup of
namespace
forminio
indeployment.yaml
but there'snamespace
setup inserviceaccount.yaml
, is that normal?I guess maybe that's why it cannot find such service account when installing milvus in different namespace.
Thanks.
The text was updated successfully, but these errors were encountered: