The inclusion of the helm_extension is excellent and allows users to add and deploy Helm charts of their choice by simply referencing them in this section.
That said, I have found it a little tricky to use if I try to add and deploy local Helm charts. This is for two reasons:
The repository key needs to be set to an empty string (since this is a local chart)
The location of the chart is not relative to the repo's root directory but relative to the helm-extension module (nebari/template/stages/08-nebari-tf-extensions/modules/helm-extension/).
the easiest way around this currently is to set an absolute path but this gets even trickier when deploying Nebari via GitOps.
Value and/or benefit
This will enable further flexibility for users who want to add and deploy their own custom charts (as I have needed to do recently).
Feature description
The inclusion of the
helm_extension
is excellent and allows users to add and deploy Helm charts of their choice by simply referencing them in this section.That said, I have found it a little tricky to use if I try to add and deploy local Helm charts. This is for two reasons:
repository
key needs to be set to an empty string (since this is a local chart)nebari/template/stages/08-nebari-tf-extensions/modules/helm-extension/
).Value and/or benefit
This will enable further flexibility for users who want to add and deploy their own custom charts (as I have needed to do recently).
Anything else?
No response