Create initial Backstage setup

[FaGru3n]

Reason We want to try out/experiment with Backstage in our platform setup to evaluate if it is helpful tool for Catena-X product teams.

To archive this, we will setup a basic backstage setup with a handful easy to configure, 'works out of the box' plugins first and later on spend potentially more time on this topic.

AC

• Create basic backstage setup on our core/infra cluster
• its reachable through a vainity url like back.demo.catena-x.net (or core? backstage?)
• We introduce basic plugins which are easy to configure/work out of box without much overhead.
  • https://github.com/backstage/backstage/blob/master/plugins/api-docs/README.md
  • See if we can incorporate our docusourus docs without changing our docusaurus setup:
  • https://backstage.io/docs/features/techdocs/techdocs-overview
  • https://backstage.io/docs/features/software-catalog/software-catalog-overview for our services like grafana
• Give the team a short overview and your expierience while configuring/setting up the plugins
• Login is possible through Github
• Bjoern has seen a demo of it
• Its mentioned in our Office Hours

Additional information / links

[FaGru3n]

Comment form @SebastianBezold topics to clarify: @Siegfriedk

Is it also ok, to have an initial test on our devsecops-testing cluster, before introducing it to the core cluster? Introducing it in the office hour seems too early, since we do not expect the teams to have any capacity to work on that. Proposal would be, that we configure 2-3 products and then have a discussion with Björn and Daniel before

[FaGru3n]

Feedback from @Siegfriedk putting it on devsecops-testing cluster would indicate its gone a week later. It should be manifested well enough that we can keep it running as it is.

We can talk to Daniel and Bjoern first sure.

[FaGru3n]

close after refinement