Carlos Esteban Lopez Jaramillo
8902c2e39d
* chore: Exporting KubernetesClientProvider as requested in issue #10457 Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com> * chore: Adding changeset Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com> * chore: Updating API reports Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com> * chore: Export auth translator contents & updating API reports Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com> * chore: Fix API reports warnings Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com> Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com> Co-authored-by: Carlos Esteban Lopez <lcarlosesteb@vmware.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.