HPE Morpheus Enterprise
1855059 Members
3439 Online
104109 Solutions
New Discussion

customOptions variable returning null in Kubernetes Blueprint YAML when using Catalog Item

 
sutt1
Senior Member

customOptions variable returning null in Kubernetes Blueprint YAML when using Catalog Item

Hi Team,

I'm trying to automate Pod deployments via Catalog Items using the Input feature to allow dynamic naming (so each deployed Pod gets a unique name). However, the variable is always rendering as null in the Blueprint YAML.

---

Environment
- HPE Morpheus Enterprise
- Blueprint Type: Kubernetes YAML Spec
- Structure: Catalog Item → Kubernetes Blueprint

---

Input Configuration
- Name: `instanceName`
- Field Name: `instanceName`
- Type: Text
- EDITABLE: checked
- The Input is attached to the Catalog Item via the Inputs section

1.png
2.png

 

 

---

Blueprint YAML (ERB)

apiVersion: apps.nvidia.com/v1alpha1
kind: NIMService
metadata:
  name: <%= customOptions.instanceName %>-gemma-3-1b
spec:
  image:
    repository: nvcr.io/nim/google/gemma-3-1b-it
    tag: "latest"
    pullPolicy: IfNotPresent
    pullSecrets:
      - ngc-secret
  authSecret: ngc-api
  storage:
    nimCache:
      name: gemma-3-1b-it-2
      profile: ''
  resources:
    limits:
      nvidia.com/gpu: 1
  expose:
    service:
      type: ClusterIP
      port: 9999
  env:
    - name: NIM_NUM_KV_CACHE_SEQ_LENS
      value: "1"
    - name: NIM_RELAX_MEM_CONSTRAINTS
      value: "1"
    - name: CUDA_MPS_PIPE_DIRECTORY
      value: /tmp/nvidia-mps

---

Problem

Even though the user fills in a value for `instanceName` in the Catalog ordering wizard, the rendered YAML shows the value as null — resulting in a Pod name like `null-gemma-3-1b` instead of `myapp-gemma-3-1b`.

3.png

 

---

What I've tried
1. Confirmed the Input (`instanceName`) is added to the Catalog Item's Inputs section
2. Enabled the `EDITABLE` checkbox on the Input definition
3. Checked the Blueprint edit screen — there is **no Inputs tab** available at the Blueprint level (only Name, Description, Category, Label, Image, and Kubernetes YAML Spec config)

---

Current issue

`customOptions.instanceName` or `customOptions['instanceName']` returns null. 

---

Questions
Are there any known issues with customOptions passing in a Catalog Item → Kubernetes Blueprint flow?

Any guidance would be appreciated. Thanks!