Open SanjayVas opened 5 months ago
Reopening this as it still happens.
Bumping this as #1785 is a pending issue from last week rotation. Although #1785 is closed, it is de-duplicated against this issue.
Manually disabled the Postgres secret rotation in AWS Secret Manager. Keep monitor whether this issue is gone.
By manually trigger the rotation in AWS Secret Manager, the error reproduced. Thus disabling the rotation will solve the issue. If the issue come back again, it could be caused by the re-deployment of RDS postgres.
I don't see any PR that updates the Terraform config here. Therefore, this issue cannot yet be marked closed. All AWS infra must be managed via Terraform.
According to @YuhongWang-Amazon, this is related to a password auto-rotation feature which results in a new K8s Secret being generated. As the Halo update process assumes that all K8s objects are only updated on apply, this feature cannot be used.