This message was deleted.
# generala
adamant-kite-43734
06/08/2023, 6:08 PMThis message was deleted.
c
creamy-pencil-82913
06/08/2023, 6:48 PMyou’re manually installing fleet, and then using it to deploy the rancher helm chart?
creamy-pencil-82913
06/08/2023, 6:48 PMI probably wouldn’t do that, I’d just use the HelmChart controller built in to RKE2
creamy-pencil-82913
06/08/2023, 6:49 PMI don’t think Rancher expects there to be an unmanaged fleet installation on the local cluster. In general, you should deploy as little as possible to the local cluster.
f
fancy-barista-28405
06/08/2023, 11:11 PMActually I'm using HelmChart controller declares in the terraform template I use to build the cluster, and being a generic cluster template for us, It installs Fleet via HelmChart which then pulls in anything cluster specific via a GitRepo and path we set when we build the cluster. That GitRepo, in some cases, needs to pull in Rancher and Vault. But of course by that time, Fleet is already installed, it pulls in Rancher into the cluster, and Rancher seems to get upset that there is already a fleet there. None of this is manual but using Fleet and HelmChart and HelmChartConfig CRDs.
fancy-barista-28405
06/08/2023, 11:13 PMThis is also the case of a fresh cluster, not one I'm trying to modify. So I'm looking for a fresh build that provides Fleet => GitRepo, that then pulls in cert-manager, vsphere sc, vault client, prometheus CRDs and then Rancher so it can get a TLS cert for its ingress.
c
creamy-pencil-82913
06/08/2023, 11:16 PMI’m not sure we’ve tested a standalone fleet deployment alongside the rancher-managed one. You might have to fuss with it a bit.
creamy-pencil-82913
06/08/2023, 11:16 PMIf rancher provides something, it generally expects to be the only deployment of that something
f
fancy-barista-28405
06/09/2023, 8:25 PMOk, thanks. I had hoped that Rancher would notice the preinstall of Fleet and simply inherit it instead of deploying its own prerequisite, since both came from the same company and used standard Rancher namespaces. I'll dig further into the mechanism going wrong.
fancy-barista-28405
06/17/2023, 9:13 PMI got it to work! When I installed the Fleet chart into the default cattle-fleet-system namespace my problem occurred where Rancher deployed an extra fleet-agent-local to my already existing one. But when I changed and deploy Fleet at boot time into the cattle-fleet-*local-*system namespace, Rancher did NOT start a duplicate fleet-agent-local and now co-exists with the boot-time Fleet deployment. They're playing well together now.
3 Views