Syncing Your Chart Repository

Note: This example is specifically for a Google Cloud Storage (GCS) bucket which serves a chart repository.

Prerequisites

  • Install the gsutil tool. We rely heavily on the gsutil rsync functionality
  • Be sure to have access to the Helm binary
  • _Optional: We recommend you set object versioning on your GCS bucket in case you accidentally delete something._

Set up a local chart repository directory

Create a local directory like we did in the chart repository guide, and place your packaged charts in that directory.

For example:

  1. $ mkdir fantastic-charts
  2. $ mv alpine-0.1.0.tgz fantastic-charts/

Generate an updated index.yaml

Use Helm to generate an updated index.yaml file by passing in the directory path and the url of the remote repository to the helm repo index command like this:

  1. $ helm repo index fantastic-charts/ --url https://fantastic-charts.storage.googleapis.com

This will generate an updated index.yaml file and place in the fantastic-charts/ directory.

Sync your local and remote chart repositories

Upload the contents of the directory to your GCS bucket by running scripts/sync-repo.sh and pass in the local directory name and the GCS bucket name.

For example:

  1. $ pwd
  2. /Users/funuser/go/src/github.com/helm/helm
  3. $ scripts/sync-repo.sh fantastic-charts/ fantastic-charts
  4. Getting ready to sync your local directory (fantastic-charts/) to a remote repository at gs://fantastic-charts
  5. Verifying Prerequisites....
  6. Thumbs up! Looks like you have gsutil. Let's continue.
  7. Building synchronization state...
  8. Starting synchronization
  9. Would copy file://fantastic-charts/alpine-0.1.0.tgz to gs://fantastic-charts/alpine-0.1.0.tgz
  10. Would copy file://fantastic-charts/index.yaml to gs://fantastic-charts/index.yaml
  11. Are you sure you would like to continue with these changes?? [y/N]} y
  12. Building synchronization state...
  13. Starting synchronization
  14. Copying file://fantastic-charts/alpine-0.1.0.tgz [Content-Type=application/x-tar]...
  15. Uploading   gs://fantastic-charts/alpine-0.1.0.tgz:              740 B/740 B
  16. Copying file://fantastic-charts/index.yaml [Content-Type=application/octet-stream]...
  17. Uploading   gs://fantastic-charts/index.yaml:                    347 B/347 B
  18. Congratulations your remote chart repository now matches the contents of fantastic-charts/

Updating your chart repository

You’ll want to keep a local copy of the contents of your chart repository or use gsutil rsync to copy the contents of your remote chart repository to a local directory.

For example:

  1. $ gsutil rsync -d -n gs://bucket-name local-dir/    # the -n flag does a dry run
  2. Building synchronization state...
  3. Starting synchronization
  4. Would copy gs://bucket-name/alpine-0.1.0.tgz to file://local-dir/alpine-0.1.0.tgz
  5. Would copy gs://bucket-name/index.yaml to file://local-dir/index.yaml
  7. $ gsutil rsync -d gs://bucket-name local-dir/       # performs the copy actions
  8. Building synchronization state...
  9. Starting synchronization
  10. Copying gs://bucket-name/alpine-0.1.0.tgz...
  11. Downloading file://local-dir/alpine-0.1.0.tgz:                        740 B/740 B
  12. Copying gs://bucket-name/index.yaml...
  13. Downloading file://local-dir/index.yaml:                              346 B/346 B

Helpful Links: * Documentation on gsutil rsync * The Chart Repository Guide * Documentation on object versioning and concurrency control in Google Cloud Storage