-
Notifications
You must be signed in to change notification settings - Fork 178
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
storage migration check error #79
Comments
Hi, Does anyone seen this error in gcp stack driver after upgrade? |
Hi there! This has been automatically marked as stale because it has not had activity in the past 14 days. It will be closed in 14 days if no further activity takes place. |
@SrikantPatil88 did you manage to fix this ? I have the same issue despite that storage object admin permission is granted |
@bluemalkin, Yes, We manage to solve the issue. The issue was the default k8’s service account required binding to the Google service account within the workload Identity. Workload Identities were added in Kubernetes 1.14 + and are required when the master nodes were upgraded. |
Thanks - I fixed my issue, I used the wrong annotation for the service account. I'm using workload identity too and it works well. You may want to close this ticket. |
My Vault cluster was working properly yesterday, after upgrade it stopped working
Getting below error in stack driver,
[WARN] storage migration check error: error="failed to read value for "core/migration": googleapi: got HTTP response code 403 with body:
AccessDenied
Access denied.The status of Vault pod,
containers with unready status: [vault]
The text was updated successfully, but these errors were encountered: