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

Add documentation that explains about use of deleteCRDResources #2949

Open
sbulage opened this issue Oct 9, 2024 · 0 comments
Open

Add documentation that explains about use of deleteCRDResources #2949

sbulage opened this issue Oct 9, 2024 · 0 comments

Comments

@sbulage
Copy link
Contributor

sbulage commented Oct 9, 2024

QA Observations:

Followed below scenario's considering the deleteCRDResources values and annotation behavior.

Scenario 1

  • Create a GitRepo which installs CRD's along with the application.(Used this fleet.yaml file.)
  • Make sure deleteCRDResources: true must be present in the fleet.yaml.
  • Verified that annotation helm.sh/resource-policy: keep is absent.

Scenario 2

  • Create a GitRepo which installs CRD's along with the application.(Used this fleet.yaml file.)
  • Update the value of deleteCRDResources: false in the fleet.yaml.
  • Verified that annotation helm.sh/resource-policy: keep is present.

Consider this conclusion for documentation.

Conclusion:

If we don't want to see annotation helm.sh/resource-policy: keep then we have to use the deleteCRDResource option with true value in fleet.yaml.

Originally posted by @sbulage in #2860 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant