Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
DiamondJoseph opened this issue May 4, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@DiamondJoseph
Copy link

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 garryod self-assigned this May 4, 2023
@garryod garryod added the enhancement New feature or request label May 4, 2023
@garryod
Copy link
Member

garryod commented May 4, 2023

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
Copy link
Author

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
Copy link
Member

garryod commented May 4, 2023

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 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants