search

parodos-dev / workflow-software-templates

Apache License 2.0
0 stars 8 forks source link

Propagate Backstage Kubernetes URL #18

Open dmartinol opened 4 months ago

dmartinol commented 4 months ago

Instead of hardcoding the K8S_CLUSTER_URL in the template, shouldn't we reuse the same as the one configured in Backstage? And BTW, what if there are many clusters configured?

masayag commented 4 months ago

For testing, it simplifies the configuration to the dev/qe to assume backstage and other services/operators are all installed on the same cluster. For that, we can obtain the K8S_CLUSTER_URL and probably also create a service account and generate the token for the K8S_CLUSTER_TOKEN.

This is less feasible for production, in which the admin may decide on the target cluster and have more than one for the different services.

dmartinol commented 3 months ago

Correct. What about to rephrase this issue like:

The software template should provide a way to select one of the K8s clusters configured in backstage as the input of the generated workflow

This way, there is no implicit selection of the target cluster, and the user can specify the one where he wants to deploy the resources with a simpiofied user interface. The assumption here is that all the managed clusters are configured in Backstage, but this should be the actual way to use it in an enterprise deployment, IIUC.