kubeshop/testkube-dashboard Docker Image Overview

kubeshop/testkube-dashboard

Testkube Kubernetes Dashboard

0 次下载

:warning: The Open Source version of the Testkube Dashboard is being deprecated.
For further details and next steps, please refer to our official announcement.

Welcome to Testkube - Your friendly cloud-native testing framework for Kubernetes

Website | Documentation | *** | Slack | Blog

Testkube Dashboard

Dashboard to manage your Testkube cluster and monitor its real-time results.

The Dashboard is deployed as an application in the cluster. It runs in a browser, and it communicates with the Testkube API Server via Ingress Controller (either provided or bundled).

Running Dashboard
1. Bundled
2. Repository
3. Docker
Configuring Application
1. Environment Variables
2. Building Docker Image
Learn More
1. Contributing and Architecture
2. Telemetry
3. Testkube

Running Dashboard

Bundled

By default, Dashboard is installed in your cluster along with your Testkube system.

To use the bundled Dashboard, run testkube dashboard command with Testkube CLI, to forward the UI and API ports from the Kubernetes cluster.

:warning: Testkube Pro and Enterprise

This Dashboard works only for the Testkube Open Source installations. To manage the Testkube in Enterprise or Pro offering, use their corresponding dashboards:

app.testkube.io for Testkube Pro

Your Enterprise URL for Testkube Enterprise

:eight_spoked_asterisk: Disable bundling dashboard

To disable Dashboard installation with the Testkube system, you may use testkube-dashboard.enabled=false value in the Helm chart.

Repository

To run the Testkube Dashboard for development:

Install Node 20.x
Fork the repository and clone it (or just clone it, if you are Testkube member or want to read it only)
Install NPM dependencies
Run npm start command

bash
git clone ***:kubeshop/testkube-dashboard.git && cd testkube-dashboard
npm install
npm start

To learn more about the Testkube Dashboard development and architecture, see the Contribution manual.

:eight_spoked_asterisk: Environment variables

To configure your environment variables, either:

create .env file in the repository, or

export the environment variables globally

You may use both build time and dynamic variables here.

Please note, that you may want to use Create React App's variables too, i.e. BROWSER=none to avoid opening the browser.

Docker

The Docker images for the Testkube Dashboard are deployed to the Docker Hub as kubeshop/testkube-dashboard.

To start Dashboard using Docker, run the image with the dynamic environment variables you would like to pass, i.e.:

bash
docker run --rm \
  -p 8080:8080 \
  -e REACT_APP_API_SERVER_ENDPOINT=[***] \
  kubeshop/testkube-dashboard:latest

:warning: Environment variables

To override the build time environment variables too, you need to build the Docker image on your own.

Configuring Application

Environment Variables

All the Dashboard is configured with the environment variables.

Part of them is included directly in the production build, while the rest may be modified for the running application.

The latest variables are listed in env.ts file, but for simplicity we keep them documented below too.

:eight_spoked_asterisk: Deep-linking overrides

You may temporarily override the variables in the running application using the query string. The Dashboard seeks for query params starting with ~ and try to override any matching known variable.

The query param name should be a variable name, but for simplicity it may omit REACT_APP_ prefix and is case-insensitive. Short name from the tables above may be used.

As an example, to change the API endpoint, you may use https://demo.testkube.io?~api_server_endpoint=http://localhost:8088.

Build Time Variables

The build time environments are loaded from process.env during build time.

Name	Short Name	Description
`REACT_APP_SENTRY_DSN`	`sentry_dsn`	Sentry DSN for error reporting
`REACT_APP_GTM_ID`	`gtm_id`	Google Tag Manager ID for telemetry
`REACT_APP_VERSION`	`version`	Dashboard version used for reporting and displaying

Dynamic Variables

The dynamic variables are loaded from automatically generated env-config.js file.

Name	Short Name	Description
`REACT_APP_API_SERVER_ENDPOINT`	`api_server_endpoint`	URL for the Testkube API Server
`REACT_APP_DISABLE_TELEMETRY`	`disable_telemetry`	Force disabling telemetry in the Dashboard
`REACT_APP_DEBUG_TELEMETRY`	`debug_telemetry`	Display debugging information about telemetry in the console log
`REACT_APP_CRD_OPERATOR_REVISION`	`crd_operator_revision`	testkube-operator's branch for getting the JSON Schema for CRDs
`REACT_APP_ROUTE_BASENAME`	`route_basename`	Basename for the application. Use only when your Dashboard is accessible via different path than `/`

Building Docker Image

To build the Docker image of Testkube Dashboard locally, simply build the Dockerfile, optionally with the environment variables from above.

bash
docker build \
  --build-arg REACT_APP_API_SERVER_ENDPOINT=[***] \
  -t kubeshop/testkube-dashboard:latest .

:eight_spoked_asterisk: Environment variables

When you are building images with docker build, you may either both set the build time variables, and set defaults for the dynamic variables.

Learn more

Contributing and Architecture

To learn more about the Testkube Dashboard development and architecture, see the Contribution manual.

Telemetry

To learn more about what custom events we expose to Google Tag Manager, see Telemetry document.

Testkube

For the documentation of the Testkube system, see docs.testkube.io.
To see the live demo, you may take a look at demo.testkube.io (some API endpoints are disabled there though, to avoid modifications)

Unleash the power of cloud native testing in Kubernetes with Testkube.

查看更多 testkube-dashboard 相关镜像 →

rancher/rio-dashboard

暂无描述

1M+ pulls

上次更新：未知

bitnami/parse-dashboard

Bitnami安全加固的Parse Dashboard镜像，用于监控和管理Parse应用，遵循安全最佳实践。

Testkube MCP Server向AI工具和工作流公开持续测试能力，包括测试编排、执行、故障排除和分析，支持通过模型上下文协议集成测试工作流。

667 pulls

上次更新：未知

apache/apisix-dashboard

Apache APISIX Dashboard是Apache APISIX的官方Web UI，旨在为用户提供友好、直观的界面以管理和运维APISIX集群，支持可视化配置路由、服务、上游、插件等核心资源，实时监控集群运行状态与流量指标，有效简化APISIX的运维复杂度，帮助用户更高效地部署、管理和维护API网关。

3810M+ pulls

上次更新：未知

轩辕镜像配置手册

探索更多轩辕镜像的使用方法，找到最适合您系统的配置方式

登录仓库拉取

通过 Docker 登录认证访问私有仓库

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

Docker Compose

Docker Compose 项目配置

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

MacOS OrbStack

MacOS OrbStack 容器配置

宝塔面板

在宝塔面板一键配置镜像

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

极空间

极空间 NAS 系统配置服务

爱快路由

爱快 iKuai 路由系统配置

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

专属域名拉取

无需登录使用专属域名

需要其他帮助？请查看我们的常见问题Docker 镜像访问常见问题解答或提交工单

镜像拉取常见问题

轩辕镜像免费版与专业版有什么区别？

免费版仅支持 Docker Hub 访问，不承诺可用性和速度；专业版支持更多镜像源，保证可用性和稳定速度，提供优先客服响应。

轩辕镜像支持哪些镜像仓库？

专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等；免费版仅支持 docker.io。

流量耗尽错误提示

当返回 402 Payment Required 错误时，表示流量已耗尽，需要充值流量包以恢复服务。

410 错误问题

通常由 Docker 版本过低导致，需要升级到 20.x 或更高版本以支持 V2 协议。

manifest unknown 错误

先检查 Docker 版本，版本过低则升级；版本正常则验证镜像信息是否正确。

镜像拉取成功后，如何去掉轩辕镜像域名前缀？

使用 docker tag 命令为镜像打上新标签，去掉域名前缀，使镜像名称更简洁。

查看全部问题→

用户好评

来自真实用户的反馈，见证轩辕镜像的优质服务

oldzhang

运维工程师

Linux服务器

"Docker访问体验非常流畅，大镜像也能快速完成下载。"

kubeshop/testkube-dashboard

Testkube Kubernetes Dashboard

0 次下载

😅 镜像要是出问题，背锅的一定是你

镜像简介版本下载

😅 镜像要是出问题，背锅的一定是你

:warning: The Open Source version of the Testkube Dashboard is being deprecated.
For further details and next steps, please refer to our official announcement.

Welcome to Testkube - Your friendly cloud-native testing framework for Kubernetes

Website | Documentation | *** | Slack | Blog

Testkube Dashboard

Dashboard to manage your Testkube cluster and monitor its real-time results.

The Dashboard is deployed as an application in the cluster. It runs in a browser, and it communicates with the Testkube API Server via Ingress Controller (either provided or bundled).

Running Dashboard
1. Bundled
2. Repository
3. Docker
Configuring Application
1. Environment Variables
2. Building Docker Image
Learn More
1. Contributing and Architecture
2. Telemetry
3. Testkube

Running Dashboard

Bundled

By default, Dashboard is installed in your cluster along with your Testkube system.

To use the bundled Dashboard, run testkube dashboard command with Testkube CLI, to forward the UI and API ports from the Kubernetes cluster.

:warning: Testkube Pro and Enterprise

This Dashboard works only for the Testkube Open Source installations. To manage the Testkube in Enterprise or Pro offering, use their corresponding dashboards:

app.testkube.io for Testkube Pro

Your Enterprise URL for Testkube Enterprise

:eight_spoked_asterisk: Disable bundling dashboard

To disable Dashboard installation with the Testkube system, you may use testkube-dashboard.enabled=false value in the Helm chart.

Repository

To run the Testkube Dashboard for development:

Install Node 20.x
Fork the repository and clone it (or just clone it, if you are Testkube member or want to read it only)
Install NPM dependencies
Run npm start command

bash
git clone ***:kubeshop/testkube-dashboard.git && cd testkube-dashboard
npm install
npm start

To learn more about the Testkube Dashboard development and architecture, see the Contribution manual.

:eight_spoked_asterisk: Environment variables

To configure your environment variables, either:

create .env file in the repository, or

export the environment variables globally

You may use both build time and dynamic variables here.

Please note, that you may want to use Create React App's variables too, i.e. BROWSER=none to avoid opening the browser.

Docker

The Docker images for the Testkube Dashboard are deployed to the Docker Hub as kubeshop/testkube-dashboard.

To start Dashboard using Docker, run the image with the dynamic environment variables you would like to pass, i.e.:

bash
docker run --rm \
  -p 8080:8080 \
  -e REACT_APP_API_SERVER_ENDPOINT=[***] \
  kubeshop/testkube-dashboard:latest

:warning: Environment variables

To override the build time environment variables too, you need to build the Docker image on your own.

Configuring Application

Environment Variables

All the Dashboard is configured with the environment variables.

Part of them is included directly in the production build, while the rest may be modified for the running application.

The latest variables are listed in env.ts file, but for simplicity we keep them documented below too.

:eight_spoked_asterisk: Deep-linking overrides

You may temporarily override the variables in the running application using the query string. The Dashboard seeks for query params starting with ~ and try to override any matching known variable.

The query param name should be a variable name, but for simplicity it may omit REACT_APP_ prefix and is case-insensitive. Short name from the tables above may be used.

As an example, to change the API endpoint, you may use https://demo.testkube.io?~api_server_endpoint=http://localhost:8088.

Build Time Variables

The build time environments are loaded from process.env during build time.

Name	Short Name	Description
`REACT_APP_SENTRY_DSN`	`sentry_dsn`	Sentry DSN for error reporting
`REACT_APP_GTM_ID`	`gtm_id`	Google Tag Manager ID for telemetry
`REACT_APP_VERSION`	`version`	Dashboard version used for reporting and displaying

Dynamic Variables

The dynamic variables are loaded from automatically generated env-config.js file.

Name	Short Name	Description
`REACT_APP_API_SERVER_ENDPOINT`	`api_server_endpoint`	URL for the Testkube API Server
`REACT_APP_DISABLE_TELEMETRY`	`disable_telemetry`	Force disabling telemetry in the Dashboard
`REACT_APP_DEBUG_TELEMETRY`	`debug_telemetry`	Display debugging information about telemetry in the console log
`REACT_APP_CRD_OPERATOR_REVISION`	`crd_operator_revision`	testkube-operator's branch for getting the JSON Schema for CRDs
`REACT_APP_ROUTE_BASENAME`	`route_basename`	Basename for the application. Use only when your Dashboard is accessible via different path than `/`

Building Docker Image

To build the Docker image of Testkube Dashboard locally, simply build the Dockerfile, optionally with the environment variables from above.

bash
docker build \
  --build-arg REACT_APP_API_SERVER_ENDPOINT=[***] \
  -t kubeshop/testkube-dashboard:latest .

:eight_spoked_asterisk: Environment variables

When you are building images with docker build, you may either both set the build time variables, and set defaults for the dynamic variables.

Learn more

Contributing and Architecture

To learn more about the Testkube Dashboard development and architecture, see the Contribution manual.

Telemetry

To learn more about what custom events we expose to Google Tag Manager, see Telemetry document.

Testkube

For the documentation of the Testkube system, see docs.testkube.io.
To see the live demo, you may take a look at demo.testkube.io (some API endpoints are disabled there though, to avoid modifications)