search

DiamondLightSource / developer-portal

A deployment of backstage for use at Diamond Light Source
Apache License 2.0
2 stars 3 forks source link

Make or find Backstage type to represent multiple deployments of a System #77

Open DiamondJoseph opened 1 year ago

DiamondJoseph commented 1 year ago

Athena system is going to be deployed on multiple beamlines. It would be convenient to have a mapping of the beamlines where it is deployed, which services are additionally included/excluded from the default set. There doesn't seem to be an existing type to represent deployment instances?

garryod commented 1 year ago

I expect integration with kubernetes (one of my todos) will solve this by providing the ability to navigate between components and their deployed instances. Is there any chance you'd be able to have a quick read of the plugin docs and let me know if it meets your requirements?

DiamondJoseph commented 1 year ago

I'm not sure if it does: looks like we could attach annotations or labels to the System, but annotations are str:str, and we'd be looking at a list of namespaces. https://backstage.io/docs/features/kubernetes/configuration#surfacing-your-kubernetes-components-as-part-of-an-entity

garryod commented 1 year ago

I believe the 'backstage.io/kubernetes-namespace' label is optional, any components with matching 'backstage.io/kubernetes-id's should be ingresses, even across multiple namespaces. But I could easily be wrong :shrug: