# @backstage/plugin-kubernetes

> A Backstage plugin that integrates towards Kubernetes

Latest version **0.12.23** (published 2026-09-15) · Apache-2.0 license · 70.5K weekly downloads

## Install

```sh
npm install @backstage/plugin-kubernetes
pnpm add @backstage/plugin-kubernetes
yarn add @backstage/plugin-kubernetes
bun add @backstage/plugin-kubernetes
```

## Health

**Score 85/100 (A)** — status: active.

Positive: has types; esm support; no vulnerabilities; recently updated; high maintenance score; high quality score; popular repo.

Warnings: pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.12.23 |
| Published | 2026-09-15 |
| First published | 2020-09-22 |
| Weekly downloads | 70.5K |
| License | Apache-2.0 |
| TypeScript types | bundled |
| Module format | ESM + CommonJS |
| Dependencies | 9 |
| Unpacked size | 194 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 34590 |
| Maintainers | patriko, freben, marcuseide |
| Keywords | backstage, kubernetes |

## Links

- npm: https://www.npmjs.com/package/@backstage/plugin-kubernetes
- Repository: https://github.com/backstage/backstage
- Homepage: https://backstage.io
- npm.io page: https://npm.io/package/@backstage/plugin-kubernetes

## Dependencies (9)

- [@material-ui/core](https://npm.io/package/@material-ui/core.md) ^4.12.2
- [@backstage/catalog-model](https://npm.io/package/@backstage/catalog-model.md) ^1.10.1
- [@backstage/core-components](https://npm.io/package/@backstage/core-components.md) ^0.18.14
- [@backstage/core-plugin-api](https://npm.io/package/@backstage/core-plugin-api.md) ^1.12.10
- [@backstage/frontend-plugin-api](https://npm.io/package/@backstage/frontend-plugin-api.md) ^0.18.1
- [@backstage/plugin-catalog-react](https://npm.io/package/@backstage/plugin-catalog-react.md) ^3.2.3
- [@backstage/plugin-kubernetes-react](https://npm.io/package/@backstage/plugin-kubernetes-react.md) ^0.6.0
- [@backstage/plugin-permission-react](https://npm.io/package/@backstage/plugin-permission-react.md) ^0.5.5
- [@backstage/plugin-kubernetes-common](https://npm.io/package/@backstage/plugin-kubernetes-common.md) ^0.9.13

## Recent versions

- 0.12.23 (latest) — 2026-09-15
- 0.0.0-nightly-20260928023907 (nightly) — 2026-09-28
- 0.12.24-next.0 (next) — 2026-09-22
- 0.0.0-nightly-20260927023342 — 2026-09-27
- 0.0.0-nightly-20260926022852 — 2026-09-26
- 0.0.0-nightly-20260925022940 — 2026-09-25
- 0.0.0-nightly-20260924023050 — 2026-09-24
- 0.0.0-nightly-20260923023054 — 2026-09-23
- 0.0.0-nightly-20260922023058 — 2026-09-22
- 0.0.0-nightly-20260921023416 — 2026-09-21
- 0.0.0-nightly-20260920023043 — 2026-09-20
- 0.0.0-nightly-20260919022921 — 2026-09-19
- 0.0.0-nightly-20260918023200 — 2026-09-18
- 0.0.0-nightly-20260909022715 — 2026-09-09
- 0.12.23-next.2 — 2026-09-08
- … 1913 more at https://npm.io/package/@backstage/plugin-kubernetes/versions

## README

# Kubernetes

Welcome to the Backstage Kubernetes frontend plugin!

This plugin exposes information about your entity-specific Kubernetes objects with a desire to provide value to the service owner, rather than just a Kubernetes cluster administrator.

It will elevate the visibility of errors where identified, and provide drill down about the deployments, pods, and other objects for a service.

It directly interfaces with the [Kubernetes Backend Plugin (`@backstage-plugin-kubernetes-backend`)](https://github.com/backstage/backstage/tree/master/plugins/kubernetes-backend).

## Introduction

See our announcement blog post [New Backstage feature: Kubernetes for Service Owners](https://backstage.io/blog/2021/01/12/new-backstage-feature-kubernetes-for-service-owners) to learn more about the motivation behind developing the plugin.

## Setup & Configuration

This plugin must be installed in a Backstage app, along with its peer backend plugin.

```bash
# From your Backstage root directory
yarn --cwd packages/app add @backstage/plugin-kubernetes
```

Once installed, the plugin is automatically available in your app through the default feature discovery. For more details and alternative installation methods, see [installing plugins](https://backstage.io/docs/frontend-system/building-apps/installing-plugins).

It requires configuration in the Backstage `app-config.yaml` to connect to a Kubernetes API control plane.

In addition, configuration of an entity's `catalog-info.yaml` helps identify which specific Kubernetes object(s) should be presented on a specific entity catalog page.

For more information, see the [formal documentation about the Kubernetes feature in Backstage](https://backstage.io/docs/features/kubernetes/overview).

### Enabling the entity content tab

Enable the Kubernetes entity content extension in your `app-config.yaml`:

```yaml
app:
  extensions:
    - entity-content:kubernetes/kubernetes
```

Now, the extension appears on your entity page as one of the tabs, which is called `KUBERNETES`.
By default, the tab will only appear on entities that are Components or Resources. You can override
that behavior by providing a config block to the extension, like so:

```yaml
app:
  extensions:
    - entity-content:kubernetes/kubernetes:
        config:
          filter:
            kind:
              $in:
                - component
                - api
                - resource
                - system
```

## Getting started

Your plugin has been added to the example app in this repository, meaning you'll be able to access it by running `yarn start` in the root directory, and then navigating to [/kubernetes](http://localhost:3000/catalog/default/component/:component-name/kubernetes).

You can also serve the plugin in isolation by running `yarn start` in the plugin directory.
This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads.
It is only meant for local development, and the setup for it can be found inside the [/dev](./dev) directory.

---
_Source: https://npm.io/package/@backstage/plugin-kubernetes · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._