-
Notifications
You must be signed in to change notification settings - Fork 229
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
[0.9] [SURE-8550] drift detection is generating secrets without cleaning #2515
Comments
/forwardport v2.9.0 |
Additional QAProblemCorrecting drift on Fleet-deployed resources would create a new Helm release, and a new SolutionHelm Rollback operations, used internally by Fleet to correct drift, now obey Fleet's global limit on Helm history, restricting the number of kept history items to 2. Testing(See repro steps above)
|
Steps performed:
Outputs:Secrets Before Upgrade
Secrets After Upgrade
Helm history before upgrade
Helm history after upgrade
|
SURE-8550
Issue description:
When enabling Self Healing (drift detection) Fleet will generate a new secret every time drift is detected. To a point where it might exhaust Rancher.
Fleet 0.9.4
Business impact:
For the customer Rancher went down due to too many secrets being cached
Troubleshooting steps:
Disabling self healing will clean the secrets
Repro steps:
helm.sh/release.v1
) will be created in the namespace for the deploymenthelm history
commands in the target namespace and specifying the Helm release name.Workaround:
Is a workaround available and implemented? yes
What is the workaround: disable self healing (disabling self healing also remove all the secrets)
Actual behavior:
Multiple secrets are created for a single "correction", and old ones are preserved.
Expected behavior:
Only 1 secret is created per "correction", while keeping the total number of Helm releases at a maximum of just 2.
Files, logs, traces:
Additional notes:
The text was updated successfully, but these errors were encountered: