Hi All,
I’m trying to create a self-service catalog that allows end-users to spin up deployments in my kubernetes cluster. Ideally, I want to have HELM charts stored in a private GitLab repo that gets pulled and installed whenever someone orders it. Currently, I’m seeing three roadblocks to this…
1 - There is no layout or node type that supports HELM charts, ideally i want to just create instance type’s that link to layouts that use the HELM chart to deploy the nodes.
2 - Regardless of that, I seem to only be able to create app blueprints for HELM charts which do not tie to any specific instance and, when viewed after provisioning, they lack data like what port users can access the service on. Can i get them as instances instead of apps? I can’t find any HELM stuff in the instance/layout/node areas…
3 - It also seems to not support templating for options (maybe because this is an app and not an instance?), as the configuration json of the catalog item isn’t a json at all, it’s a YAML that doesn’t seem to accept the options i put in there (i.e. trying to give it a dynamic name)
I must be doing something terribly wrong but I’m at a loss for documentation on this subject (there’s a HELM page, but not much on what i’m looking for catalog-item-wise).
If it helps, this is some of the catalog config for my app… all the input / options don’t get templated and just end up as-is 
…
name: xxxx-<%= customOptions.mph_application_name %>-<%= customOptions.mph_tier %>
group:
id: 1
code: ‘’
defaultPool:
id: 12
name: core-k8s / web-apps
isSelected: false
environment: Test
…
Anyway… i’m very confused and probably over my head lol… any help is greatly appreciated!
Thanks for the nudge in the right direction!