Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploying minio and milvus as statefulsets #217

Open
nairan-deshaw opened this issue Dec 2, 2024 · 4 comments
Open

Deploying minio and milvus as statefulsets #217

nairan-deshaw opened this issue Dec 2, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@nairan-deshaw
Copy link

Currently, in standalone mode, the operator creates deployment for minio and milvus which leads to an issue where we do a rolling restart and the old pod still is mounted to the PVC. This creates a deadlock where the new one is not able to start and the old one does not die. Is there a way to configure these as statefulsets / change the update strategy to Recreate?

@haorenfsa
Copy link
Collaborator

For milvus, you can explicitly set spec.components.enableRollingUpdate to false.
And for minio, I'm not very sure, but you could try setting spec.dependencies.storage.inCluster.values.DeploymentUpdate.type to Recreate

@haorenfsa
Copy link
Collaborator

Em... There is a bug in setting spec.components.enableRollingUpdate to false. You may not be able to make the strategy to Recreate. I'll fix this later.

@haorenfsa haorenfsa added the bug Something isn't working label Dec 2, 2024
@haorenfsa haorenfsa self-assigned this Dec 2, 2024
@nairan-deshaw
Copy link
Author

Is there a way to deploy these as statefulsets instead?

@haorenfsa
Copy link
Collaborator

No for Milvus.
For minIO, if you specify the cluster mode of it, it will become a statefulset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants