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

Workload in holoinsight-server should use persistent storage volume #647

Open
ideal opened this issue Sep 7, 2023 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@ideal
Copy link

ideal commented Sep 7, 2023

Describe this problem

In holoinsight-server, there are ceresdb, es, mongo, mysql, prometheus, currently none declares using persistent volume claim, so it fallbacks to anonymous docker volume specified in Dockerfile.

But if you delete the pod to restart it, or the pod is shifted to other node, the data will be lost, e.g. for holoinsight-mysql-0.

To Reproduce

kubectl delete po -n holoinsight-server holoinsight-mysql-0

Expected behavior

mysql data should be retained, but if you login into mysql, the databases and tables disappear.

Additional Information

No.

@ideal ideal added the bug Something isn't working label Sep 7, 2023
@xzchaoo
Copy link
Contributor

xzchaoo commented Sep 20, 2023

Hi @ideal . Thanks for the feedback.
As you said. The Chart currently provided is not enough for production-level deployment. Some improvements are needed in the future.

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