Grafana in modified state after installing via HelmOps in `Fleet 0.14.5` and `0.13.10-beta.1`

[mmartin24]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Same issue as #4655 but in 0.14.5 and 0.13.10-beta.1 now with Rancher

Current Behavior

Issue.

Installing this chart via HelmOps leaves the bundle in modified state with display message:

Modified(1) [Bundle test-grafana]; deployment.apps default/test-grafana modified {"spec":{"strategy":{"rollingUpdate":null}}}

---

Note this was and still is correctly working in Rancher prime 2.13.4 with Fleet 0.14.4. See test link passing:

Expected Behavior

Should be deployed

Steps To Reproduce

Steps To Reproduce

Deploy Rancher 2.13 (I did it with v2.13-be6d3fa0f22f35a2a6c43514ec0bcb8469f8450a-head with Fleet 0.14.5-beta-1
Upload the following yaml in HelmOps

apiVersion: fleet.cattle.io/v1alpha1
kind: HelmOp
metadata:
  name: test-grafana
  annotations:
  namespace: fleet-local
spec:
  correctDrift:
    enabled: false
  helm:
    chart: grafana
    repo: https://grafana.github.io/helm-charts

Environment

- Architecture: amd64/arm64
- Fleet Version: 0.14.5-beta1 and 0.14.5-beta2
- Cluster:
  - Provider:k3w
  - Options:
  - Kubernetes Version: 1.33.1+k3s1

Logs

Anything else?

No response

[p-se]

/backport v2.12

[rancherbot]

Not creating port issue, milestone v2.12 does not exist or is not an open milestone

[p-se]

/backport v2.12.9