-
Notifications
You must be signed in to change notification settings - Fork 6
Home
Here we will list some common issues and their solutions.
ConfigMaps and secrets do not automatically reload on deployed pods when you update them with the same name. This is why we have config map version numbers for most services. Increment that number will trigger a redeployment of the associated pods. Otherwise you need to retrigger deployment via kubernetes (there are many ways to do this).
The PCG service likely requires a service account key to access or write to some resource, and that service account key has expired. Look through the service accounts you have added to the PCG service and find the expired one and get an updated key from wherever you were given it. You can find a list of the relevant service accounts in the secret folder in your CAVEdeployment repository.
You can check the key expirations dates by following those steps:
- Open the service account cloud console page
- For each service account under
Keysyou find the expiration date of each key
Update expired keys using those steps:
- If expired, click
Add Key>Create new key, and download the.jsonfile - paste the content of the json file in the respective secret in
CAVEdeployment/secrets/$ENVIRONMENT/$FILENAME.json. - rerun
./infrastructure/$ENVIRONMENT/secrets.sh
create_service_accounts.sh throws (gcloud.iam.service-accounts.keys.create) FAILED_PRECONDITION: Precondition check failed
Most likley, your service accounts have already 10 keys associcated with them. You will need to delete some keys from each affected service account to fix this problem. To do that follow those steps:
- Open the service account cloud console page and select the relevant project
- find the service account and click on it, and then click on keys
- the
Add Keybutton will be disabled if 10 keys are present already - if that is the case delete some of the older keys
- now, create_service_accounts.sh should not throw the error anymore