Closed ngrkajac closed 2 months ago
The issue was triggered by the credential rotations by the SRE team.
The credential rotation resulted in the update of the secret cloud-manager-env-gcp
. This update was only detected by the GCP Authentication check, while the GCP service API calls were still using the old credentials and failing with 500 error responses.
The issue is fixed now in the following PRs:
Description Search logs for
Invalid JWT Signature.
Expected result
Actual result
Steps to reproduce
Troubleshooting