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

Instruction for configuring general velero chart #16

Open
tareksha opened this issue Dec 10, 2019 · 3 comments
Open

Instruction for configuring general velero chart #16

tareksha opened this issue Dec 10, 2019 · 3 comments

Comments

@tareksha
Copy link

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.

@tareksha
Copy link
Author

I've got it to work. This is the required values.yaml override in the public chart:

initContainers:
- image: registry.cn-hangzhou.aliyuncs.com/acs/velero-plugin-alibabacloud:v1.2
  name: velero-plugin-alibabacloud
  volumeMounts:
  - mountPath: /target
    name: plugins
configuration:
  provider: alibabacloud
  backupStorageLocation:
    name: alibabacloud
    bucket: <BUCKET>
  extraEnvVars:
    ALIBABA_CLOUD_ACCESS_KEY_ID: <KEY_ID>
    ALIBABA_CLOUD_ACCESS_KEY_SECRET: <KEY_SECRET>
    ALIBABA_CLOUD_OSS_ENDPOINT: <ENDPOINT>
credentials:
  useSecret: false

@haoshuwei
Copy link
Member

@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.

@haoshuwei
Copy link
Member

Waiting for PR #2152 and PR #27 to be merged and release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants