Files

T

Jamie Klassen a5a9d3318a don't surface non-FetchErrors

It makes sense to gracefully show an error that was actually related to fetching
data from Kubernetes, but if the error is happening for some other exotic
reason, the default error handling logic in Backstage should take over and
log/manage it appropriately.

Signed-off-by: Jamie Klassen <jklassen@vmware.com>

2022-12-14 17:51:19 -05:00

examples/dice-roller

…

src

don't surface non-FetchErrors

2022-12-14 17:51:19 -05:00

.eslintrc.js

…

.snyk

kubernetes-backend: ignore taffydb vulnerability

2022-09-07 22:24:09 +02:00

api-report.md

node-fetch-based implementation for pod metrics

2022-12-14 17:51:19 -05:00

CHANGELOG.md

Version Packages (next)

2022-12-13 16:56:03 +00:00

config.d.ts

clusters in app-config support caFile

2022-12-02 18:23:18 -05:00

package.json

Version Packages (next)

2022-12-13 16:56:03 +00:00

README.md

…

README.md

Kubernetes Backend

This is the backend part of the Kubernetes plugin for Backstage. It is called by and responds to requests from the frontend @backstage/plugin-kubernetes plugin.

It directly interfaces with the Kubernetes API control plane to obtain information about objects that will then be presented at the front end.

Introduction

See our announcement blog post New Backstage feature: Kubernetes for Service Owners to learn more about the motivation behind developing the plugin.

Setup & Configuration

This plugin must be explicitly added to a Backstage app, along with it's peer frontend plugin.

The plugin 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.