opencost.ui.uiPath configuration in helm chart

[gkfabs]

I see the uiPath in the PR 298 is only used in template configmap-frontend.yaml. I was expecting it also in template deployment.yaml to add an argument ui_path as explained in the original PR 106

[gustavo-sdo]

This behavior is actually expected, @gkfabs.

The ui.uiPath parameter only works when using a custom-built opencost-ui image, because the UI application is compiled and the base path cannot be changed dynamically at runtime via container arguments or environment variables.

As documented in the opencost-ui README, the base UI path must be defined at build time using a build-arg:

https://github.com/opencost/opencost-ui?tab=readme-ov-file#overriding-the-base-ui-url-path

Example:

docker build \
  --build-arg ui_path=/my/custom/path \
  -t custom-opencost-ui:latest .

Because of this:

• Setting ui.uiPath in the Helm chart has no effect when using the default upstream image
• Passing --ui_path as a runtime argument in the Deployment would not solve the issue

---

Full Example

Below is a full example of how to build and deploy a custom UI image with a non-root base path (this is how I’m using it on my side):

1. Clone the repository:

git clone https://github.com/opencost/opencost-ui.git

2. Enter the project and define the required parameters:

cd opencost-ui

# Docker Hub, ECR, or another registry
export REGISTRY_HOST=your_registry_address

# OpenCost UI version
export IMAGE_TAG=1.118.0

3. Build the image with the desired base path:

docker build \
  --no-cache \
  --build-arg ui_path=/my/custom/path \
  --tag $REGISTRY_HOST/myrepo/opencost-ui:$IMAGE_TAG .

4. Push the image to your registry:

docker push $REGISTRY_HOST/myrepo/opencost-ui:$IMAGE_TAG

5. Finally, ensure your Helm (or HelmRelease) manifest references the custom-built image:

spec:
  values:
    opencost:
      ui:
        image:
          registry: your_registry_address
          repository: myrepo/opencost-ui
          tag: "1.118.0"

Replace the registry, repository, and tag values according to your setup.

[ameijer]

reviewed this during community meeting - seems to be WAI as per @gustavo-sdo , closing