-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Description
The helm-ci orb currently doesn't run helm dependency build or update, so will fail if the chart being checked has any dependencies unless the dependencies were committed to the repo as well.
This is an issue when trying to use it to lint charts that use KMI provided charts as dependencies.
To enhance this to support KMI my suggestion is to:
- switch to
cimg/base:stableimage - add the
circleci/aws-ecr@7.2.0andcircleci/helm@2.0.0orbs - run
helm/install-helm-clientto install the helm client
This should be backwards compatible.
To then handle dependencies via the KMI helm repo, the following env variables would need to be provided:
AWS_ACCESS_KEY_ID=<provided by #kaluza-managed-infra>AWS_SECRET_ACCESS_KEY=<provided by #kaluza-managed-infra>AWS_REGION=eu-west-1AWS_ECR_ACCOUNT_URL=215727133225.dkr.ecr.eu-west-1.amazonaws.comHELM_EXPERIMENTAL_OCI=1
To pull dependencies it would then need to:
- run
aws-ecr/ecr-loginto login to ECR - run
aws ecr get-login-password --region eu-west-1 | helm registry login --username AWS --password-stdin ${AWS_ECR_ACCOUNT_URL}to login to the KMI helm repo - run
helm dependency buildorupdatebefore linting.
I've implemented something like this for the event-streaming-platform-kmi-gitops repo, and can prepare a PR for this too if there's interest.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels