Skip to main content

Publish a marketplace package

Make a helm chart installable from the marketplace UI. Optional typed install form via x-form-schemas.

Who can do this​

  • Anyone with marketplace:create permission in the org. Default developer and admin roles have it.
  • For globally-shared packages, only super-admins via Admin → Marketplace, and only when the license carries MaxPublicMarketplacePackages > 0.

Add a package​

Sidebar → Marketplace → Add Package.

Fill in:

  • Name + slug — slug is auto-generated from name; edit if needed. Slug is the stable URL piece.
  • Description + icon URL — what users see in the catalog
  • Categories — multi-select from the global taxonomy. Helps users find your package. Add tags for the chart's domain (networking, storage, observability, …).

Chart source​

Two source flavours:

  • From a registered registry — pick one of your org's registries from the dropdown, type the chart name (without the registry URL prefix). DT Edge Platform constructs the chart_ref from registry URL + chart name. Recommended.
  • Manually-entered chart_ref — for one-off public-repo charts you don't want to register fully. Type the full chart reference (e.g. oci://public-charts.example.com/foo). The registry field stays blank.

Save. The package appears in the org's marketplace with 0 versions so far.

Add a version​

Click into the package → Versions tab → Add version.

  • Version — semver (e.g. 1.2.3). Shows in the install drawer's version dropdown.
  • Chart version — the chart's helm version. Often equals Version; differs when you're packaging a downstream variant.
  • Default values (YAML) — what users see pre-filled in the YAML editor on install. Empty is fine; helm uses the chart's built-in defaults.
  • Form schema (x-form-schemas, optional but encouraged) — see below

Save. The version appears in the install drawer immediately for anyone in the org.

x-form-schemas — typed install forms​

If you want users to install via a friendly form rather than hand-edited YAML, embed an x-form-schemas block in the default values:

x-form-schemas:
  schema:
    type: object
    properties:
      replicaCount:
        type: integer
        title: Replicas
        minimum: 1
        default: 2
      image:
        type: object
        properties:
          tag:
            type: string
            title: Image Tag
            default: "1.2.3"
  ui:
    replicaCount: { ui:widget: number }

The DT Edge Platform UI reads this on install, renders typed inputs with labels + validation, and serialises the result back into values.yaml on submit. JSON Schema (Draft 7) is supported, plus a small ui: extension for widgets (number / password / textarea / select / radio / checkbox).

When x-form-schemas is missing, the install drawer only shows the YAML editor.

Image registries (extra)​

If your chart pulls images from registries other than its own chart registry, link them to the package:

  • Package detail → Image Registries tab → Add
  • Pick from your org's registries with is_image_registry=true

At install time, DT Edge Platform wires creds for all of these into the namespace (union with the chart's own registry if that one's also marked as an image registry, and any image_registry_ids the install request explicitly carries).

Edit / delete​

Same actions menu on the package row:

  • Edit — change name / slug / description / icon / categories / source
  • Delete — refuses if active releases on the cluster reference this package's chart_ref; check the Applications list first

Per-version edits via the Versions tab. Deleting a version that existing releases pinned to is allowed — those releases keep running, but you can't re-install or upgrade-to that version afterwards.

Visibility​

  • Org-scoped packages — only members of your org see them
  • Globally shared packages — super-admin publishes via Admin → Marketplace. Only surfaces in the admin UI when the active license carries MaxPublicMarketplacePackages > 0.

If you want a chart usable by every org in this install, ask your admin to publish it globally rather than each org publishing their own copy.

Common errors​

  • Slug already in use — pick a different slug; uniqueness is per-org for org-scoped packages
  • Chart not found at publish-time — DT Edge Platform optionally probes the registry when you save; failure means the chart_ref + version isn't reachable. Check registry creds, chart name, version pin
  • YAML schema validation failed — your x-form-schemas block doesn't parse as JSON Schema. The error message includes the offending path.

See also​