Files
backstage/plugins/kubernetes-backend
Brian Fletcher b08ea0d2ec add ability to specify an external id for assumed role for k8
From the AWS documentation.

A cross-account role is usually set up to trust everyone in an account.
Therefore, the administrator of the trusting account might send an external
ID to the administrator of the trusted account. That way, only someone with
the ID can assume the role, rather than everyone in the account.

Signed-off-by: Brian Fletcher <brian@roadie.io>
2021-08-06 17:34:48 +01:00
..
2021-07-30 12:28:39 +02:00
2021-08-05 00:24:56 +00:00
2021-01-25 14:42:33 -05:00

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.