Update Helm chart for aiq2-web: rename application, bump version to 2…

[AjayThorve]

…603.16.0-rc12, and update image repository tags for aiq-agent and aiq-frontend.

[greptile-apps]

Greptile Summary

This PR updates the Helm chart for the AI-Q web deployment: it renames the chart from aiq-web to aiq2-web, bumps the chart version to 2603.16.0-rc12, and populates the previously empty image repositories with real NGC registry paths (nvcr.io/nvidia/blueprint/aiq-agent and nvcr.io/nvidia/blueprint/aiq-frontend) at tag 2.0.0. The sub-chart archive aiq-0.0.4.tgz is also updated.

Key changes:

• Chart name renamed from aiq-web → aiq2-web (breaking change for existing Helm releases — helm upgrade against an old release will require attention)
• Chart version bumped from 2603.15.0-rc11 → 2603.16.0-rc12
• aiq-agent and aiq-frontend image repositories populated with NGC paths (previously empty strings, making the chart non-deployable without overrides)
• Image tags changed from date-based format (2603.15.ext.rc11) to semantic versioning (2.0.0), diverging from the chart's own date-based versioning scheme
• Binary sub-chart aiq-0.0.4.tgz updated (contents not directly inspectable in review)

Confidence Score: 4/5

• Safe to merge for new deployments; operators with existing Helm releases should be aware of the breaking chart rename before upgrading.
• Changes are straightforward: a chart rename, version bump, and populating previously-empty image registry paths. No logic errors or security issues are introduced. The main concern is the breaking nature of the chart rename for in-place upgrades, and the versioning format divergence between chart and images — both are documentation/process concerns rather than runtime bugs.
• The binary deploy/helm/deployment-k8s/charts/aiq-0.0.4.tgz cannot be inspected directly in review — verify its contents are correct before merging.

Important Files Changed

Filename	Overview
deploy/helm/deployment-k8s/Chart.yaml	Chart renamed from aiq-web to aiq2-web and version bumped to 2603.16.0-rc12; rename is a breaking change for existing Helm releases.
deploy/helm/deployment-k8s/values.yaml	Image repositories for aiq-agent and aiq-frontend now populated with NGC registry paths; image tags changed from date-based format to 2.0.0 semantic version, which diverges from the chart's date-based versioning scheme.
deploy/helm/deployment-k8s/charts/aiq-0.0.4.tgz	Binary sub-chart archive updated; contents cannot be directly inspected in review — verify the packaged chart includes expected changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Helm Chart: aiq2-web\nv2603.16.0-rc12"] --> B["Sub-chart: aiq v0.0.4\n(aiq-0.0.4.tgz)"]
    B --> C["backend deployment\nnvcr.io/nvidia/blueprint/aiq-agent:2.0.0"]
    B --> D["frontend deployment\nnvcr.io/nvidia/blueprint/aiq-frontend:2.0.0"]
    B --> E["postgres deployment\nbitnami/postgresql:latest"]

    C -->|"port 8000"| F["aiq-backend Service\nClusterIP"]
    D -->|"port 3000"| G["aiq-frontend Service\nClusterIP + Ingress (nginx)"]
    E -->|"port 5432"| H["aiq-postgres Service\nClusterIP"]

    C -->|"DB URL"| H
    D -->|"BACKEND_URL"| F

Loading

Comments Outside Diff (2)

1. deploy/helm/deployment-k8s/values.yaml, line 37-38 (link)

   Image tag versioning inconsistency

   The chart version uses a date-based versioning scheme (2603.16.0-rc12) while the image tags for both aiq-agent and aiq-frontend now use semantic versioning (2.0.0). This divergence makes it harder to correlate which chart release corresponds to which image release when debugging deployments or rolling back.

   If both images are intended to be pinned together at 2.0.0, this is fine as a one-time alignment, but it's worth documenting the versioning convention going forward (e.g., in the README) so that future bumps follow a consistent scheme across chart and image tags.

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

2. deploy/helm/deployment-k8s/Chart.yaml, line 2 (link)

   Breaking rename for existing Helm releases

   Renaming the chart from aiq-web to aiq2-web is a breaking change for any environment that has an existing Helm release of this chart. Helm tracks the chart name in release metadata, so a helm upgrade against an existing aiq-web release using this renamed chart will either fail or silently create a mismatch in the release history.

   Existing operators will need to either:

   • Run helm uninstall <release> followed by a fresh helm install, or
   • Be aware that the chart identity has changed.

   This is worth calling out explicitly in the PR description or in an upgrade guide so operators aren't caught off-guard.

_{Last reviewed commit: 98d691c}