Closed floreks closed 2 weeks ago
how do you customize the helm values for installing our agent in the cluster w/ this structure?
i think a single crd to install vcluster + agent is not a bad idea (my original thought was you'd just use a service deployment for the vcluster though), but we also need to be able to specify agent helm values and helm repository
Oh wait there's helm values for vcluster plus the agent, that's nice
I think we should still want to support separately created vclusters. So if we could add a bool field to the spec specifying maybe external
and bypass the creation of the vcluster helm chart (so either people can manage that themselves, via Plural service deployment or loft.sh's tooling) they would be able to.
Ok, so when external flag is set then we only upsert to the API, install the agent using provided kubeconfig ref and skip the vcluster chart installation?
Ok, so when external flag is set then we only upsert to the API, install the agent using provided kubeconfig ref and skip the vcluster chart installation?
Yeah precisely
template
package to be able to reuse added repositoriesCRD
CRD (for testing locally)