We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
QA Observations: Followed below scenario's considering the deleteCRDResources values and annotation behavior.
Followed below scenario's considering the deleteCRDResources values and annotation behavior.
deleteCRDResources
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.
GitRepo
deleteCRDResources: true
fleet.yaml
helm.sh/resource-policy: keep
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.
deleteCRDResources: false
Consider this conclusion for documentation.
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.
deleteCRDResource
true
Originally posted by @sbulage in #2860 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Consider this conclusion for documentation.
Conclusion:
If we don't want to see annotation
helm.sh/resource-policy: keep
then we have to use thedeleteCRDResource
option withtrue
value infleet.yaml
.Originally posted by @sbulage in #2860 (comment)
The text was updated successfully, but these errors were encountered: