Kubernetes Web View’s behavior and appearance can be customized for the needs of your organization:

  • resource type links shown in the Sidebar can be customized to add CRDs, or to optimize for frequent access
  • default Label & Custom Columns can be defined to show values of standardized object labels (e.g. “app”, “version”, etc)
  • External Links can be added to link objects to monitoring tools, internal application registries, custom UIs, etc
  • the Search can be customized to search in CRDs, or to cover frequent search cases
  • setting Preferred API Versions allows forcing the use of specific/newer Kubernetes API versions
  • one of the Themes can be selected as default, or you can create your own CSS theme
  • HTML Templates can be customized to match your branding, to add static links, and to inject custom JS/CSS
  • Static Assets can be included to add images, JS, or CSS files
  • Prerender Hooks can be used to add or transform view data

Label & Custom Columns

Most organizations have a standard set of labels for Kubernetes resources, e.g. all pods might have “app” and “version” labels. You can instruct Kubernetes Web View to show these labels as columns for the respective resource types via the --default-label-columns command line option.

Example command line argument to show the “application” and “version” labels for pods and the “team” label for deployments:


Note that the label names are separated by comma (“,”) whereas multiple different entries for different resource types are separated by semicolon (“;”).

Users of the web UI can remove the pre-configured label columns by passing a single comma as the labelcols query parameter: /clusters/../namespaces/_all/pods?labelcols=,.

You can hide existing columns via the --default-hidden-columns command line option, e.g. to remove the “Nominated Node” and “Readiness Gates” columns from pod tables:

--default-hidden-columns=pods=Nominated Node,Readiness Gates

Arbitrary custom columns can be defined with JMESPath expressions, e.g. add a column “Images” for pods and the column “Strategy” for deployments:


Multiple column definitions are separated by a single semicolon (“;”) whereas multiple different entries for different resource types are separated by two semicolons (“;;”). Please be aware that custom columns require one additional Kubernetes API call per listing.

Preferred API Versions

You might want to change the default preferred API version returned by the Kubernetes API server. This is useful to force using a later/newer API version for some resources, e.g. the Kubernetes HorizontalPodAutoscaler has a different spec for later versions.

Here the example CLI option to force using new API versions for Deployment and HPA (the default is autoscaling/v1 as of Kubernetes 1.14):



Kubernetes Web View ships with a number of color (CSS) themes. You can choose a default theme for your users via --default-theme and/or limit the selection via --theme-options. Available themes are:

Flatly in night mode: dark background, blue and green as primary colors, see darkly demo
Kubernetes Web View default theme: white background, blue as primary color, see default demo
Flat and thick: white background, blue and green as primary colors, see flatly demo
Shades of gunmetal grey: dark grey background, grey colors, see slate demo
The brave and the blue: dark background, orange navbar, see superhero demo

You can use one of the Bulmaswatch themes to create your own.

HTML Templates

Custom Jinja2 HTML templates can override any of the default templates. Mount your custom templates into kube-web-view’s pod and point the --templates-path to it.

Here some of the common templates you might want to customize:

The main HTML layout (contains <head> and <body> tags).
Optional extra content for the <head> HTML part. Use this template to add any custom JS/CSS.
The top navigation bar.
Template for the left sidebar, customize this to add your own links. Note that you can change the list of resource types without touching HTML via --sidebar-resource-types, see the sidebar section.
Footer element at the end of the HTML <body>.

You can find all the standard templates in the official git repo:

You can build your own Docker image containing the templates or you can use a volume of type emptyDir and some InitContainer to inject your templates. Example pod spec with a custom footer:

  - name: generate-templates
    image: busybox
    command: ["sh", "-c", "mkdir /templates/partials && echo '<footer class=\"footer\">YOUR CUSTOM CONTENT HERE</footer>' > /templates/partials/footer.html"]
    - mountPath: /templates
      name: templates

  - name: kube-web-view
    # see
    image: hjacobs/kube-web-view:latest
    - --port=8080
    - --templates-path=/templates
    - containerPort: 8080
        path: /health
        port: 8080
    - mountPath: /templates
      name: templates
      readOnly: true
        memory: 100Mi
        cpu: 5m
        memory: 100Mi
      readOnlyRootFilesystem: true
      runAsNonRoot: true
      runAsUser: 1000
  - name: templates
      sizeLimit: 50Mi

Static Assets

As you might want to add or change static assets (e.g. JS, CSS, images), you can point Kubernetes Web View to a folder containing your custom assets. Use the --static-assets-path command line option for this and either build a custom Docker image or mount your asset directory into the pod.

Prerender Hooks

The view data (context for Jinja2 template) can be modified by custom prerender hooks to allow advanced customization.

For example, to add generated custom links for deployments to the resource detail view, create a coroutine function with signature like async def resource_view_prerender(cluster, namespace, resource, context) in a file

async def resource_view_prerender(cluster, namespace: str, resource, context: dict):
    if resource.kind == "Deployment":
        link = {
            "href": f"{resource.labels['pipeline-id']}/{resource.labels['deployment-id']}",
            "class": "is-link",
            "title": "Pipeline link",
            "icon": "external-link-alt",

This file would need to be in the Python search path, e.g. as in the root (“/”) of the Docker image. Pass the hook function as --resource-view-prerender-hook=hooks.resource_view_prerender to Kubernetes Web View.

Note that you can also do more advanced stuff in the prerender hook, e.g. call out to external systems to look up additional information.