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
I might be wrong but I've noticed that the helm chart provided with the plugin is basically a specially configured version of the general helm chart of velero that can be used for aws & azure: https://github.com/helm/charts/tree/master/stable/velero
Maybe we should have instructions for configuring the general chart to work with the velero plugin instead of creating an incompatible fork? We maintain a multi-cloud deployment where we configure and install the same helm charts for several installations and velero is the only chart that is completely different between different providers instead of simply having different values.
The text was updated successfully, but these errors were encountered:
@tareqhs Sorry for the late reply and thanks for your comments and work. Yes, you are right, we should make this plugin deployed using helm chart with different values, i will add the instructions as soon as possible.
Hi,
I might be wrong but I've noticed that the helm chart provided with the plugin is basically a specially configured version of the general helm chart of velero that can be used for aws & azure:
https://github.com/helm/charts/tree/master/stable/velero
Maybe we should have instructions for configuring the general chart to work with the velero plugin instead of creating an incompatible fork? We maintain a multi-cloud deployment where we configure and install the same helm charts for several installations and velero is the only chart that is completely different between different providers instead of simply having different values.
The text was updated successfully, but these errors were encountered: