Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

correctDrift.enabled: false in fleet.yaml has no effect #2158

Open
1 task done
jhoblitt opened this issue Feb 16, 2024 · 5 comments
Open
1 task done

correctDrift.enabled: false in fleet.yaml has no effect #2158

jhoblitt opened this issue Feb 16, 2024 · 5 comments
Labels
kind/bug status/waiting Waiting for reporter

Comments

@jhoblitt
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

---
defaultNamespace: rook-ceph
labels:
  bundle: &name rook-ceph-conf
helm:
  releaseName: *name
  atomic: false
  takeOwnership: true
  timeoutSeconds: 3600
correctDrift:
  enabled: false
dependsOn:
  - selector:
      matchLabels:
        bundle: rook-ceph-cluster

Results in

kind: Bundle
metadata:
  creationTimestamp: "2024-02-16T15:46:21Z"
  generation: 4
  labels:
    bundle: rook-ceph-conf
    fleet.cattle.io/commit: 0b0dcfb9ff35d561e2ae52356f9aeddb2d636864
    fleet.cattle.io/repo-name: kueyen
  name: kueyen-fleet-lib-rook-ceph-conf
  namespace: fleet-default
  resourceVersion: "120977600"
  uid: d6fb879b-88e9-4a06-914f-bf9571bb5947
spec:
  correctDrift:
    enabled: true
  defaultNamespace: rook-ceph
  dependsOn:
  - selector:
      matchLabels:
        bundle: rook-ceph-cluster

When correctDrift.enabled: true is set on the associated GitRepo resource.

Expected Behavior

I would expect that it is possible to set all BundleDeploymentOptions from a fleet.yaml file and that these options would override values set in the GitRepo resource.

Steps To Reproduce

  1. Create a GitRepo resource with correctDrift.enabled: true.
  2. Create a fleet.yaml with correctDrift.enabled: false
  3. Inspect the generated bundle

Environment

- Architecture: amd64
- Fleet Version: 0.9.0
- Cluster:
  - Provider: rke1
  - Options:
  - Kubernetes Version: 1.25.9

Logs

No response

Anything else?

Possibility related to #1794 and #2001?

@jhoblitt
Copy link
Contributor Author

jhoblitt commented Apr 4, 2024

I'm wondering if this might already be fixed in 0.9.1 via #1982. Rancher 2.8.3 was tagged a few days ago and bundles fleet 0.9.2, so I hope to test this soon.

@manno
Copy link
Member

manno commented Apr 17, 2024

Is this bug fixed by Fleet >0.9.0?

@manno manno added the status/waiting Waiting for reporter label Apr 17, 2024
@jhoblitt
Copy link
Contributor Author

I will try to retest today.

@jhoblitt
Copy link
Contributor Author

jhoblitt commented Sep 4, 2024

This still isn't working in 0.9.8 and 0.10.1.

@jhoblitt
Copy link
Contributor Author

jhoblitt commented Oct 2, 2024

This is still present in 0.10.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug status/waiting Waiting for reporter
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants