Cluster Registry Client Chart

Helm chart for Cluster Registry Client.

Prerequisites for installing the chart

Notes

Secret management must be handled by the user. Secrets must be created (either with kubectl or with a secret management tool) beforehand in order for the chart deployment to be successful. This step is mandatory for the application to run succesfully.

Required secret name is cluster-registry-aws and required keys are: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, SQS_AWS_REGION, SQS_ENDPOINT, SQS_QUEUE_NAME

Example of a secret name and corresponding required keys (used in deployment.yaml file):

apiVersion: v1
data:
  AWS_ACCESS_KEY_ID: <AWS_ACCESS_KEY_ID_VALUE>
  AWS_SECRET_ACCESS_KEY: <AWS_SECRET_ACCESS_KEY_VALUE>
  SQS_AWS_REGION: <SQS_AWS_REGION_VALUE>
  SQS_ENDPOINT: <SQS_ENDPOINT_VALUE>
  SQS_QUEUE_NAME: <SQS_QUEUE_NAME_VALUE>
kind: Secret
metadata:
  name: cluster-registry-aws
  namespace: <namespace>
type: Opaque

Chart configuration

To see a full list if configurable parameters, check the table generated in the README.md file.

Deploying the chart

Adding the cluster-registry helm repository

helm repo add <release> https://opensource.adobe.com/cluster-registry
helm repo update

Installing the chart

helm install <release> cluster-registry/cluster-registry-client --namespace <namespace>

Adding the cluster-registry-client chart as a dependency

- name: cluster-registry-client
  version: <version>
  repository: "https://opensource.adobe.com/cluster-registry"

helm dependency update cluster-registry-client

Checking the chart version

helm search repo cluster-registry-client