Files

T

blam 101978963d Merge branch 'master' of github.com:spotify/backstage into migrate-to-msw

* 'master' of github.com:spotify/backstage: (139 commits)
  Cleanup
  Update PinButton.test.tsx
  feat: update github insights plugin version (#2973)
  Ignore IntelliJ *.iml files (#2971)
  chore(deps): bump rollup-plugin-dts from 1.4.11 to 1.4.13
  fix the plugin card on plugins page
  align 'Add to Marketplace' button on plugins page
  fix the PluginGrid on mobiles sizes
  use getBy query instead of queryBy when asserting for elements present in document (#2951)
  Update PinButton.tsx
  Add test case for Progress component (#2953)
  fix the styling of footer copy on mobile
  add changeset
  handle the case where no entities are available to show
  core-api: work around issue with ApiRef export const declarations
  core-api: move utility api system implementation into apis/system
  Update docs regarding npm config ignore-scripts flag
  Another try
  Fix Core Features configuration id (#2948)
  Fix test?
  ...

2020-10-19 23:57:40 +02:00

dev

Kubernetes plugins boilerplate (#2559 )

2020-09-22 15:47:27 +01:00

src

Merge branch 'master' of github.com:spotify/backstage into migrate-to-msw

2020-10-19 23:57:40 +02:00

.eslintrc.js

Kubernetes plugins boilerplate (#2559 )

2020-09-22 15:47:27 +01:00

package.json

Merge branch 'master' of github.com:spotify/backstage into migrate-to-msw

2020-10-13 03:56:13 +02:00

README.md

update kubernetes readmes (#2781 )

2020-10-07 15:49:49 +01:00

README.md

kubernetes

Welcome to the kubernetes plugin!

This plugin was created through the Backstage CLI

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.

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 directory.

Surfacing your Kubernetes components as part of an entity

Adding the entity annotation

In order for Backstage to detect that an entity has Kubernetes components, the following annotation should be added to the entity.

annotations:
  'backstage.io/kubernetes-id': dice-roller

Labeling Kubernetes components

In order for Kubernetes components to show up in the service catalog as a part of an entity, Kubernetes components must be labeled with the following label:

'backstage.io/kubernetes-id': <ENTITY_NAME>