Skip to main content
DT Cloud DT Edge Platform is the edge-computing offering of DT Cloud - Türkiye’s hyper-scalable, self-service cloud computing platform, built around full data compliance and digital sovereignty. It manages Kubernetes edge instances, a private image registry, a Helm marketplace, virtual machines, and monitoring from a single console. If your cluster is connected to the DT Edge Platform, you can install and upgrade BenchGen entirely from its UI instead of running Helm yourself. DT Edge Platform stores the chart versions in its marketplace, applies your values, and then tracks the release - pods, logs, metrics, and storage - per edge instance. You still need everything from the Helm prerequisites in place on the target cluster: ingress controller, cert-manager, the dockerhub-creds pull secret, and DNS for every hostname in your values.

​
Air-gapped environments

DT Edge Platform is built for air-gapped installs: every image is served from the platform registry, not from the public internet. The container runtime on each edge node mirrors docker.io through the registry’s pull-through proxy (the dockerhub-proxy project), so the chart’s canonical image names keep working with zero values changes - pulls never leave the platform. For a fully offline site, pre-load all chart images into the platform registry before installing. Alternatively, mirror the images under your own registry namespace and override the repositories in values - see the Helm values reference (image.* for the core components; the agentspace service images live inside each service’s containers list in the chart defaults, so overriding one means copying that whole list). Either way, the pull secret (dockerhub-creds by default) must hold credentials for the registry the images are actually pulled from.

​
1. Find the package in the Marketplace

Open Marketplace in the left sidebar and locate the benchgen package. Every published chart version is available under one card - the version is selected at install time.
DT Edge Platform marketplace with the benchgen Helm package

The benchgen package in the DT Edge Platform marketplace

If the package is missing, add it with Add Package (upload the chart .tgz or point at the chart repository). Packages added with organization scope are visible to your whole organization.

​
2. Install

Click Install on the benchgen card and fill in the dialog:
Install benchgen dialog in DT Edge Platform

Install dialog - version, target instance, release name, namespace, and values

The values editor is pre-filled with the chart defaults. Replace its content with your own values file - the same one you would pass to helm -f, with all CHANGE-ME placeholders and hostnames filled in. Click Install. DT Edge Platform runs the Helm install, including the bootstrap hooks (migrations and the two admin-init jobs).

​
3. Track the release in Applications

The release appears under Applications with its namespace, edge instance, and Helm status:
Applications list showing the benchgen release as deployed

The deployed release in the Applications list

Open the application to see the release details - chart version, revision, deploy time - plus live Metrics (CPU/memory per pod), Logs, Workloads, Pods, Storage, and Network tabs:
benchgen application details with CPU and memory metrics

Release details: status, revision, and per-pod metrics

A healthy install shows status deployed and all pods Running (the hook jobs show as Completed).

​
4. Upgrade

Open the application and click Upgrade:
Upgrade benchgen dialog in DT Edge Platform with the values editor

Upgrade dialog - pick a chart version and edit the release values

  1. Select the chart version. You can keep the current version to apply a values-only change, or pick a newer one from the marketplace.
  2. Edit the values YAML - the editor is pre-filled with the release’s current values.
  3. Confirm. Only pods whose rendered spec changed are restarted; data on PersistentVolumeClaims survives.
To remove the release, use Uninstall on the application page. Mind the data warning: chart-managed PVCs are deleted with the release.
Last modified on July 17, 2026