feat: Ephemeral cluster

[arunvthangaraj]

Description of changes:

This PR adds a backstage template to deploy a ephemeral k8s cluster to the management cluster.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[elamaran11]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

[elamaran11]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

[arunvthangaraj]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

@elamaran11 Yes the backstage template does deploy a argocd app which uses vcluster helm chart to deploy the virtual cluster to management cluster.

[elamaran11]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

@elamaran11 Yes the backstage template does deploy a argocd app which uses vcluster helm chart to deploy the virtual cluster to management cluster.

@arunvthangaraj Understood, thanks for the clarity. One question though, does this work even if the backstage template is invoked multiple times for creating multiple vClusters by different personas at the same time?

[elamaran11]

@csantanapr Review this from your end.

[arunvthangaraj]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

@elamaran11 Yes the backstage template does deploy a argocd app which uses vcluster helm chart to deploy the virtual cluster to management cluster.

@arunvthangaraj Understood, thanks for the clarity. One question though, does this work even if the backstage template is invoked multiple times for creating multiple vClusters by different personas at the same time?

yes it will work. One caveat though it will create multiple vclusters in the same namespace since the namespace is hard coded in the argo app. Do i need to make the namespace dynamic based on the name ?

[elamaran11]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

@elamaran11 Yes the backstage template does deploy a argocd app which uses vcluster helm chart to deploy the virtual cluster to management cluster.

@arunvthangaraj Understood, thanks for the clarity. One question though, does this work even if the backstage template is invoked multiple times for creating multiple vClusters by different personas at the same time?

yes it will work. One caveat though it will create multiple vclusters in the same namespace since the namespace is hard coded in the argo app. Do i need to make the namespace dynamic based on the name ?

If thats the case, It should work to support across different namespaces.

[arunvthangaraj]

@arunvthangaraj Are you not deploying vCluster on Management Cluster thru ArgoCD. The expectation is to have vCluster i stalled thru ArgoCD and accessed via CLI in workshop like this https://github.com/cnoe-io/stacks/tree/main/vcluster-multi-env/vcluster

@elamaran11 Yes the backstage template does deploy a argocd app which uses vcluster helm chart to deploy the virtual cluster to management cluster.

@arunvthangaraj Understood, thanks for the clarity. One question though, does this work even if the backstage template is invoked multiple times for creating multiple vClusters by different personas at the same time?

yes it will work. One caveat though it will create multiple vclusters in the same namespace since the namespace is hard coded in the argo app. Do i need to make the namespace dynamic based on the name ?

If thats the case, It should work to support across different namespaces.

ok will push a change for this then. Will let you all know when i complete validating the changes in a TE.