{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/339", "result": {"data":{"issuesJson":{"id":"56726e62-815f-5517-b7f4-9f32d8167bf1","title":"benc-uk/kubeview: Kubernetes 集群可视化器和图形浏览器","number":339,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposbenc-uk/kubeview
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n

KubeView

\n

\nKubernetes cluster visualiser and visual explorer\n

KubeView displays what is happening inside a Kubernetes cluster (or single namespace), it maps out the API objects and how they are interconnected. Data is fetched real-time from the Kubernetes API. The status of some objects (Pods, ReplicaSets, Deployments) is colour coded red/green to represent their status and health

\n

The app auto refreshes and dynamically updates the view as new data comes in or when it changes.

\n

Currently displays the following Kubernetes objects:

\n\n

Status

\n

\"\"
\n\"\"
\n\"\"

\n

Note. No secrets are exposed by the Kubeview API, values are redacted and replaced with __VALUE REDACTED__ before being sent.

\n

Demo & Screenshots

\n

Short video demo

\n

\"\"

\n

Screenshots

\n

\"demo\"
\n\"demo2\"

\n

Application Components

\n

The app consists of two separate but connected elements, in the standard pattern of backend REST API and JS client frontend

\n\n

Repo Details

\n

This projects follows the 'Standard Go Project Layout' directory structure and naming conventions as described here

\n\n

Docker Image

\n

Builds of the Docker image are hosted publicly on GitHub Container Registry here: https://github.com/users/benc-uk/packages/container/package/kubeview

\n\n

Helm Chart

\n

Helm chart called 'kubeview' is provided in the charts directory to help deploy and install KubeView into your cluster. The chart is also available in packaged form, in the releases section

\n

Use the supplied sample example-values.yaml file (copy it to a new name, e.g. myvalues.yaml) to configure how to deploy KubeView. The main choice is if you want to expose the service via an ingress ingress.enabled: true or a load-balancer service ingress.enabled: false

\n

When using an Ingress additionally configure the DNS hostname and TLS certs if you want to use HTTPS

\n

Cluster or Namespaced Deployment

\n

the chart supports deployment in a single namespace, set limitNamespace: true. In this mode, KubeView will be limited to displaying only the namespace it is deployed into (via the helm --namespace flag), and the namespace picker will not be shown in the UI. The ServiceAccount/Role/Binding will be scoped to this namespace too, rather than cluster wide.

\n

This is passed to the server via the NAMESPACE_SCOPE env variable

\n

Usage

\n

Deploy with the standard Helm install command:

\n
cd charts\nhelm install kubeview ./kubeview -f myvalues.yaml\n
\n

Project Meta

\n

Known Issues

\n\n

Todo / Roadmap

\n\n

Change Log

\n

See releases

","updatedAt":"2025-05-21T16:09:28Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"K8S-Cluster-Manage","color":"249bda"}},{"node":{"name":"benc-uk","color":"0b6a27"}}]},"comments":{"edges":[]}}},"pageContext":{"number":339,"previous":{"title":"instrumenta/kubeval: 验证您的 Kubernetes 配置文件，支持多个不同版本的 Kubernetes","number":338},"next":{"title":"kubewall/kubewall: 一个轻量的 k8s 集群控制面板，一个二进制即可部署，用在本地使用还是不错的。","number":340}}}, "staticQueryHashes": ["151096407","2861350382"]}