Hey hello guys, I'm looking to deploying the same helm chart multiple times to the same cluster, just changing the release name and values file parameters, wondering if this is possible to do? I'm experimenting with the multi-cluster examples but having trouble to figure out if this should work.

One of my gitrepos currently stucks in

Out of Sync

and even a

Force Sync

does not help

Is there a way to debug/see values.yaml produced after applying all labels to target cluster?

Nvm, I’ve found bundleDeployments object within a cluster namespace

I am using

secretKeyRef

but seems it's not picked up by fleet.

helm:
  valuesFrom:
    - secretKeyRef:
        name: clusterconfig
        namespace: cattle-gatekeeper-system
        key: values.yaml

Whereas the secret

clusterconfig

is in ns

cattle-gatekeeper-system

in the target (downstream) cluster

Hello! I am new to Rancher and Fleet. I am trying to implement Fleet inside Rancher. I have a Helm chart to deploy an application into a cluster, and am using different values files for Dev, Staging and Production. Using Helm I can easily choose a different values file depending on where I am deploying. I have Fleet working inside Rancher to deploy the app, but I see no way to tell it what values file to use. And I have tried searching the subject with no joy so far. Can someone point me in the right direction?

Hello! I have a fleet where I setup PVC using git repo, but somehow this pvc gets deleted in certain cases during update, I don't know the root cause, but is there any good practice with fleet? or in general I have retainPolicy Delete currently

I use NFS CSI

Hello everybody! Can we run multiple fleet-controllers? Our current fleet controller is eating up a lot of resources, and we wonder if increasing the number of replicas of the controller would help?

Fleet + Kustomization + PVC yaml seems to delete on pod crash or OOMKill, I'm still testing if it's true

Howdy, I’m trying to run fleet-0.6-rc.2 and agent deploy stuck in redeploy loop. Fleet is standalone and cluster is local. Anybody have a workaround? This is not an upgrade but just a new installation. I suspect issue is here: https://github.com/rancher/fleet/blob/master/pkg/controllers/cluster/import.go#L94 as I don’t see spec.DeployedGeneration isn’t set

Is there any way to turn off polling the GitRepo? With a webhook, the polling should not be required, right? This: https://fleet.rancher.io/webhook says:

I am playing with fleet's test mode

fleet test

and I want to pass labels to it, but something doesn't work. I have created a

fleet.yaml

and running this command:

docker run \
   -it \
   -v `pwd`:/manifests \
   --rm \
   --name fleet \
   --entrypoint sh rancher/fleet-agent:v0.3.9 \
   -c "cd /manifests && fleet \
   --debug test \
   -t devmode \
   -l env=dev"

but it's like

env=dev

is not being set. Also, is it possible to set it so that

global.fleet.clusterLabels.env

will turn to

dev

?

I’m trying to setup a repo that will contain the base-config of our 30+ downstream clusters, however i’m facing some issues when trying to deploy Helm charts along our normal “static” manifests. Currently we use the Kustomize approach with a number of servicemonitors, prometheusrules etc as described here: https://github.com/rancher/fleet-examples/tree/master/multi-cluster/kustomize Now we would also like this repo to contain/deploy some external Helm Chart like

loki-stack

and

rancher-monitoring

, sort of like this: https://github.com/rancher/fleet-examples/blob/master/multi-cluster/helm-external/fleet.yaml Is it possible to combine these into one Repo that fleet can use to deploy “everything” ? Or do you need seperate “Kustomize Repo” and “Helm Chart Repo” ? Thanks

Is it possible to do manual sync by disabling downstream clusters doing polling?

Is there a way of configuring prometheus alerts or slack notifications when a GitRepo state is different from "READY/ACTIVE"? E.g. when it is "Modified" or "Err" send a slack notification

I am trying to use multiple yaml files in my helm chart depending on the environment. I have a fleet.yaml and a GitRepo like this and am trying to edit the GitRepo but keep getting an error inside Rancher. When I make the change in Rancher it gives me this error: Operation cannot be fulfilled on gitrepos.fleet.cattle.io "logapi-dev": the object has been modified; please apply your changes to the latest version and try again Does anyone know what I am doing wrong?

targetCustomizations:
- name: development
  helm:
    valuesFiles:
    - development.yaml
  clusterName: alphadev

- name: staging
  helm:
    valuesFiles:
    - staging.yaml
  clusterName: alphadev

- name: production
  helm:
    valuesFiles:
    - values.yaml
  clusterName: alphadev

From
targets:
  - clusterName: alphadev

To
targets:
  - name: development
  clusterName: alphadev

Hello all, I have Rancher 2.7.1 running on a GKE cluster, and am attempting to add the first Git repo to Continous Delivery/Fleet. After getting through some SSH auth issues, seems like it’s able to check out the repository fine, but it is not creating any bundles or resources. The fleet.yaml in the repository is pretty simple.

kind: GitRepo
apiVersion: <http://fleet.cattle.io/v1alpha1|fleet.cattle.io/v1alpha1>
metadata:
  name: simple
  namespace: fleet-local
spec:
  repo: <https://github.com/rancher/fleet-examples>
  paths:
  - simple

Any suggestions on how to troubleshoot this? The UI shows no errors, and the step-git-source container in the gitrepo pod shows it successfully cloned the repository.

Not 100% sure, but did you select a 'target' in the GitRepo too? This might help: https://fleet.rancher.io/gitrepo-targets

We are using fleet do deploy a few basic infrastructure apps to our clusters. Although we are using GKE with Kubernetes 1.24.9, we get the following error in fleet:

Chart requires kubeVersion: >= 1.21.0-0 which is incompatible with Kubernetes v1.20.0

Any ideas how to resolve this issue? Why does Helm (?) think that is running against K8s 1.20?!

I do have a GitRepo with 3 paths, 1*helmchart, 2*kustomize. Is it normal that fleet creates a helmchart (or at least a helm-secret) for each of the kustomize-folders?

Hi, I'm unable to edit a GitRepo configuration because the resource version continuously changes. Have you experienced this? How can I edit the GitRepo without recreate it?

Hello everybody, I'm contacting you because I'm trying to set up Keda and as usual I want to use Fleet to deploy its objects. Keda is installed (still KubeVersion problem but that's not the topic here. I deployed a fleet that contains a helm chart of a project of mine with, among other things, two deployments and 2 ScaledObject. Just like the HPAs, Keda modifies the replicas so I added a diff in fleet and it works fine. On the other hand, ScaledObject objects have an “Activating” status when the trigger is pending. This is a normal status (from what I understand). But Rancher sees it in error on its UI and the bundle is also in error.

NotReady(1) [Bundle ebad]; scaledobject.keda.sh ebad-ma7/ebad-back error] Scaling is not performed because triggers are not active, Resource is Ready; scaledobject.keda.sh ebad-ma7/ebad-back modified {"spec":{"triggers":[{"metadata":{"desiredReplicas":"2","end":"35 14 * * *","start":"29 14 * * *","timezone":"Europe/Paris"},"type":"cron"}]}}; scaledobject.keda.sh ebad-ma7/ebad-front error] Scaling is not performed because triggers are not active, Resource is Ready

Is there a way to ignore this type of status? I think it's related to this issue: https://github.com/rancher/fleet/issues/937

is there a way to patch resource coming from a helm chart with kustomize?

Question... it has occurred now many times that resources delete (on sync) and cause rewrite of resources?? causes some downtime, it is also possible that on sync resources are not available and hence it happens, is there any threshold?

Hi folks! I was reading over the Fleet documentation regarding how a

GitRepo

is mapped to clusters, as well as the

ClusterGroup

concepts, and they're both using label selectors if I'm not mistaken. I'm wondering - is there a doc or proposal for how Fleet manages the case where the set of clusters matching the label selector changes? In "normal" kube, e.g. a

NodeSelector

will allow for transparent selection, movement, re-scheduling, etc - is that also what happens in Fleet?

it syncs indeed, occasionally

Sorry, not sure my question was phrased well - for instance, if I have some

GitRepo

that should select

region=us-west,cloud=aws,machine-type=xxl

or whatever, will I get instant failover if a cluster in that

ClusterGroup

goes down? Is there anything that balances out the usage of the group so, as an admin providing these clusters, I have less maintenance to do?

Has anyone used fleet to deploy the Rancher applications (https://git.rancher.io/charts) across multiple downstream clusters? I'm particularly interested in trying to roll out Rancher CIS Benchmarking.