Does anyone use Fleet to deploy clusters from Rancher? Like, have fleet manage a resource that will provision a new cluster.

helm charts & kustomize yamls

installing apps in a CD way

with combination of keel.sh

Is there a way to have a fleet repo that contains like a main helm chart but then but some inline yaml manifest inside the fleet.yaml to deploy custom resources for the helm chart?

I have rancher 2.7.5 with fleet and one imported managed kubernetes 1.25. There are a few deployments via fleet. My question is, I remove the imported kubernetes and all the fleet deployment gets deleted. Is this normal?

Hi, all I am trying to create/add a helm chart hook job : https://helm.sh/docs/topics/charts_hooks/ using kustomize from fleet. Meaning that I am adding a new manifest for the job with fleet as:

kustomize:
  dir: ./kustomize

But it seems that is not working. The job never gets deleted after :

"<http://helm.sh/hook-delete-policy|helm.sh/hook-delete-policy>": hook-succeeded

Is this suppose to work from fleet? If yes can you provide an example please.

Hi in the fleet.yaml I would like to use

sprig

if possible and do :

targetCustomizations:
    - name: local
      clusterSelector:
        matchLabels:
          provider: local
      helm:
        values:
          host: "${if .ClusterLabels.env=="qa"} value ${else} other_value ${end}"

Meaning if a label ( e.g.

.ClusterLabels.env

) has a specific value and set a helm value:

host:"${if .ClusterLabels.env=="qa"} value ${else} other_value ${end}"

hello, are canary releases possible with fleet? some reference implementation you could point me to?

I’m thinking out loud - I have this setup where I have a simple Fleet GitRepo, it triggers a Helm install nicely after a commit to the separate repo, I’m setting the image tag I want to deploy as a Helm value in the repository with

fleet.yaml

file and it works, right? Can I do it other way? For example, I’d send an webhook event when the image is built, put the tag in the event body and make Fleet catch is somehow, is it possible?

(Hi everyone BTW 👋 )

When editing a cluster in rancher 2.7.6, this dropdown doesn't contain the version that the cluster is currently at...so I can't update users. Any idea how to get the dropdown to refresh?

hi, i have a question regarding labels with fleet deployments. i am using the following in my fleet.yaml from the docs:

# All labels on Rancher clusters are available using global.fleet.clusterLabels.LABELNAME
  # These can now be accessed directly as variables
  # The variable's value will be an empty string if the referenced cluster label does not
  # exist on the targeted cluster
    variableName: global.fleet.clusterLabels.LABELNAME

is it possible to also use Node labels? the elemental node labels would be perfect for my helm deployment as i would need the serial number, which is already provided automatically as label to the node

machineInventoryLabels:
  machineUUID: ${System Information/UUID}
  manufacturer: ${System Information/Manufacturer}
  productName: ${System Information/Product Name}
  serialNumber: ${System Information/Serial Number}

clusterSelector? otherwise other selectors are on deployment level to the selected cluster

so that would go to helm values if you are using charts where applicable

Is it possible to mark a resource to not be deleted when the bundle is deleted? flux has the following annotation

<http://kustomize.toolkit.fluxcd.io/prune|kustomize.toolkit.fluxcd.io/prune>: disabled

to do this - is there a fleet equivalent? I don't want to enable this for the entire GitRepo - only for some resources.

Rancher 2.7.6... fleet doesn't work with git+ssh... connects and fetches data as it seems, then git updating error doesn't say much, I used ssh keys first ed25519 type then rsa with same results, then I suspected yamls being UTF-8 with BOM, also didn't help, then switched to HTTP(S) then it worked

Hello I use fleet and deploy per cluster an application. I use a fleet file and change the configuration with "clusterSelector". This works perfectly. but now I want to install the same application twice on the cluster with only one fleet file. Until now I have not found a way to configure this. Do you know a way?

2 fleet files

in each you define different releaseName if you're using in the same namespace

Assuming "Helm" installation

Hi, running into trouble with the Fleet v0.8.0 release. Consider the following fleet.yaml

defaultNamespace: ns-test2
namespaceLabels:
  foo: barLabel
  <http://pod-security.kubernetes.io/enforce|pod-security.kubernetes.io/enforce>: restricted
  <http://pod-security.kubernetes.io/enforce-version|pod-security.kubernetes.io/enforce-version>: latest
namespaceAnnotations:
  foo: barAnnotation
kustomize:
  dir: overlays

and then the following:

#overlays/kustomization.yaml

resources:
- ./secret.yaml
- ./namespace.yaml

and

#overlays/namespace.yaml

apiVersion: v1
kind: Namespace
metadata:
  labels:
    <http://pod-security.kubernetes.io/enforce|pod-security.kubernetes.io/enforce>: restricted
    <http://pod-security.kubernetes.io/enforce-version|pod-security.kubernetes.io/enforce-version>: latest
  name: ns-test2

and

#overlays/secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: dotfile-secret
data:
  .secret-file: dmFsdWUtMg0KDQo=

I would expect to see the namespace

ns-test2

to get created with the pss labels, but they aren't. Instead I get the following error:

Unable to continue with install: Namespace "ns-test2" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>": must be set to "Helm"; annotation validation error: missing key "<http://meta.helm.sh/release-name|meta.helm.sh/release-name>": must be set to "something"; annotation validation error: missing key "<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>": must be set to "ns-test2"]; namespace.v1 ns-test2 missing

Note I redacted it a bit

Strange thing is that the namespace is created and with the labels and annotations specified in the

fleet.yaml

.

I see I made a mistake in

fleet.yaml

. This is what it looks like:

defaultNamespace: ns-test2
namespaceLabels:
  foo: barLabel
namespaceAnnotations:
  foo: barAnnotation
kustomize:
  dir: overlays

You don't need namespace.. it is created with defaultNamespace, if I understand correctly

and it will fail if it already exists

then I get this error:

Internal error occurred: failed calling webhook "rancher.cattle.io.namespaces.create-non-kubesystem": failed to call webhook: Post "<https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation/namespaces?timeout=10s>": context deadline exceeded

more specific:

ErrApplied(1) [Bundle development-apps-tools-ns-test: Internal error occurred: failed calling webhook "rancher.cattle.io.namespaces.create-non-kubesystem": failed to call webhook: Post "<https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation/namespaces?timeout=10s>":

image.png

interesting