Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helm-ci support for dependencies #438

Open
kkonstan-ovo opened this issue May 25, 2022 · 0 comments
Open

helm-ci support for dependencies #438

kkonstan-ovo opened this issue May 25, 2022 · 0 comments

Comments

@kkonstan-ovo
Copy link

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:

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-1
  • AWS_ECR_ACCOUNT_URL=215727133225.dkr.ecr.eu-west-1.amazonaws.com
  • HELM_EXPERIMENTAL_OCI=1

To pull dependencies it would then need to:

  • run aws-ecr/ecr-login to 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 build or update before 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant