KoB
ce3639c588
* feat: add persistent volumes rendering Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add pv status Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add volume status and volume type Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add test for pv Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add persistent volume claims Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add persistent volume status pending Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add persistent volume metadata Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add persistent volume claims metadata Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: add persistent volume claims test code Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: changeset Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: remove gcp and gke.io Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: yarn build:api-reports Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: update pv to table drawer like pod Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * feat: update pvc to table drawer like pod Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: remove user event at test code Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: exclude pv,pvc from default objects Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: remove duplication import for pv Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: yarn build:api-reports Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: retrigger required checks Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: retrigger required checks Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: retrigger required checks Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> * chore: retrigger required checks Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.com> --------- Signed-off-by: 김병준 <kingbj0429@gmail.com> Signed-off-by: KoB <63000843+kingbj940429@users.noreply.github.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.