Is there an existing issue for this?
Current Behavior
I am attempting to use the experimental downstreamResources feature by assigning a unique secret to individual clusters, I am doing this by targeting a specific cluster by name, and assigning a secret to that cluster, see example below for more details.
Expected Behavior
I would expect helmop.spec.targets.downstreamResources and helmop.spec.targets.helm to work in the same way. I expect the secret I define in helmop.spec.targets.downstreamResources to be passed to the specific cluster targeted.
Steps To Reproduce
The following HelmOp is a slightly cut down version of what I am using. The HelmOp targets clusters in the "developmet" group, with the fleet.application.deploy/democratic-nfs: "true" label, all of those clusters should get the dev-nfs-driver-config pushed down to them from fleet-default in the rancher cluster, but they do not, no secret is pushed to the development clusters.
---
apiVersion: fleet.cattle.io/v1alpha1
kind: HelmOp
metadata:
name: democratic-nfs
namespace: fleet-default
spec:
defaultNamespace: democratic-nfs
helm:
chart: democratic-csi
releaseName: democratic-nfs
repo: https://democratic-csi.github.io/charts/
takeOwnership: true
values:
csiDriver:
fsGroupPolicy: File
name: org.democratic-csi.nfs
driver:
config:
driver: freenas-api-nfs
storageClasses:
- allowVolumeExpansion: true
defaultClass: false
mountOptions:
- noatime
- nfsvers=3
- nolock
name: truenas-nfs
parameters:
detachedVolumesFromSnapshots: "false"
fsType: nfs
reclaimPolicy: Delete
volumeBindingMode: Immediate
version: 0.15.1
targets:
- clusterGroup: development
clusterSelector:
matchLabels:
fleet.application.deploy/democratic-nfs: "true"
downstreamResources:
- kind: Secret
name: dev-nfs-driver-config
helm:
values:
driver:
existingConfigSecret: dev-nfs-driver-config
name: development
Environment
- Architecture: x86_64
- Fleet Version: v0.14.3
- Cluster:
- Provider: Harvester
- Options: Nothing special/relevant
- Kubernetes Version: v1.34.3+rke2r1
Logs
Anything else?
No response
Is there an existing issue for this?
Current Behavior
I am attempting to use the experimental
downstreamResourcesfeature by assigning a unique secret to individual clusters, I am doing this by targeting a specific cluster by name, and assigning a secret to that cluster, see example below for more details.Expected Behavior
I would expect
helmop.spec.targets.downstreamResourcesandhelmop.spec.targets.helmto work in the same way. I expect the secret I define inhelmop.spec.targets.downstreamResourcesto be passed to the specific cluster targeted.Steps To Reproduce
The following HelmOp is a slightly cut down version of what I am using. The HelmOp targets clusters in the "developmet" group, with the
fleet.application.deploy/democratic-nfs: "true"label, all of those clusters should get thedev-nfs-driver-configpushed down to them from fleet-default in the rancher cluster, but they do not, no secret is pushed to the development clusters.Environment
Logs
Anything else?
No response