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

When there are two sets of storage in a Kubernetes cluster, one is Ceph and the other is OpenEBS, what if some applications use Ceph storage and others use OpenEBS storage when utilizing Liqo? #2642

Open
lzj09 opened this issue Jul 23, 2024 · 2 comments
Labels
kind/bug Something isn't working

Comments

@lzj09
Copy link

lzj09 commented Jul 23, 2024

When there are two sets of storage in a Kubernetes cluster, one is Ceph and the other is OpenEBS, what if some applications use Ceph storage and others use OpenEBS storage when utilizing Liqo?

@lzj09 lzj09 added the kind/bug Something isn't working label Jul 23, 2024
@tonyjuvea
Copy link

I think you're going to need to point your applications to the specific persistent volumes you would need then to depend on. However, I don't think OpenEBS indipendantly support multi-clusters like ceph does. With open ebs you're going to have to implement some other tooling such as Portworx.

@lzj09
Copy link
Author

lzj09 commented Jul 26, 2024

I think you're going to need to point your applications to the specific persistent volumes you would need then to depend on. However, I don't think OpenEBS indipendantly support multi-clusters like ceph does. With open ebs you're going to have to implement some other tooling such as Portworx.

Thank you for your reply.

What I mean is that after setting up Liqo, there will be a virtual Storage Class Liqo, but my cluster has two real Storage Classes, and Liqo will only use the default real Storage Class, the other one will not be used unless the other is set as the default real Storage Class. This operation is not very good, so there should be a rule setting to allow the virtual Storage Class liqo to choose the real Storage Class.

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

No branches or pull requests

2 participants