Skip to content

Latest commit

 

History

History
54 lines (43 loc) · 2.35 KB

quickstart_helm.md

File metadata and controls

54 lines (43 loc) · 2.35 KB
Raw

Quickstart with Helm

If you are looking to deploy all Gen3 services, that can be done via the Gen3 Helm chart. Instructions for deploying all Gen3 services with Helm can be found here.

To deploy the peregrine service:

helm repo add gen3 https://helm.gen3.org
helm repo update
helm upgrade --install gen3/peregrine

These commands will add the Gen3 helm chart repo and install the peregrine service to your Kubernetes cluster.

Deploying peregrine this way will use the defaults that are defined in this values.yaml file

You can learn more about these values by accessing the peregrine README.md

If you would like to override any of the default values, simply copy the above values.yaml file into a local file and make any changes needed.

To deploy the service independant of other services (for testing purposes), you can set the .postgres.separate value to "true". This will deploy the service with its own instance of Postgres:

  postgres:
    separate: true

You can then supply your new values file with the following command:

helm upgrade --install gen3/peregrine -f values.yaml

If you are using Docker Build to create new images for testing, you can deploy them via Helm by replacing the .image.repository value with the name of your local image. You will also want to set the .image.pullPolicy to "never" so kubernetes will look locally for your image. Here is an example:

image:
  repository: <image name from docker image ls>
  pullPolicy: Never
  # Overrides the image tag whose default is the chart appVersion.
  tag: ""

Re-run the following command to update your helm deployment to use the new image:

helm upgrade --install gen3/peregrine

You can also store your images in a local registry. Kind and Minikube are popular for their local registries:

Dependencies: Please review the "Quick Start with Helm" guides to deploy these two services.