vmware-tanzu/helm-charts

backupstoragelocation can't be completely configured via Helm

Open

#294 opened on Aug 16, 2021

View on GitHubContributor guide
 (7 comments) (2 reactions) (0 assignees)Mustache (404 forks)auto 404
good first issuevelero

Repository metrics

Stars
 (312 stars)
PR merge metrics
 (PR metrics pending)

Description

I'm installing velero using the helm chart https://github.com/vmware-tanzu/helm-charts/releases/tag/velero-2.23.3 with Minio as the backing S3 service.

The backupstoragelocation was never progressing to the Available phase and backups were failing. I looked at this documentation: https://velero.io/docs/v1.6/troubleshooting/#is-velero-using-the-correct-cloud-credentials, under the Troubleshooting BackupStorageLocation credentials header, regarding the .spec.credential.key and .spec.credential.name fields. So I hand-patched those into the backupstoragelocation in the cluster with values cloud and cloud-credentials respectively and suddenly everything worked. (I was already patching in the caCert field.)

Problem is, the helm chart does not appear to provide a way to do that. The backupstoragelocation.yaml in the templates directory and the values.yaml do not appear to have have a way to specify this, so it looks like I need to patch it after the chart deploys. Do you think I'm missing something?

Thanks.

Contributor guide

Research direction
Add support for configuring `.spec.credential.name` and `.spec.credential.key` in the Helm chart's values.yaml and update the backupstoragelocation template accordingly.
Tech stack
kubernetes
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HelmKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65