Matthew Clarke
c010632f88
* kubernetes-plugin: integrate with top method from kubernetes client library Signed-off-by: mclarke <mclarke@spotify.com> * fix existing tests Signed-off-by: mclarke <mclarke@spotify.com> * prettier Signed-off-by: mclarke <mclarke@spotify.com> * add fetcher test Signed-off-by: mclarke <mclarke@spotify.com> * update api report Signed-off-by: mclarke <mclarke@spotify.com> * fix fe tests Signed-off-by: mclarke <mclarke@spotify.com> * fe tests Signed-off-by: mclarke <mclarke@spotify.com> * changeset Signed-off-by: mclarke <mclarke@spotify.com> * add skip metrics lookup flag Signed-off-by: mclarke <mclarke@spotify.com> * add skip metrics lookup to gke locator and docs Signed-off-by: mclarke <mclarke@spotify.com> * fix tests Signed-off-by: mclarke <mclarke@spotify.com> * minor change Signed-off-by: mclarke <mclarke@spotify.com> * missed prettier Signed-off-by: mclarke <mclarke@spotify.com> * missed file Signed-off-by: mclarke <mclarke@spotify.com> * more details to changeset Signed-off-by: mclarke <mclarke@spotify.com>
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.