Patroni pod health checks #436
Conversation
…bcgov/wps into task/patroni_cluster_health/405
There was a problem hiding this comment.
Just that switch to using an environment variable: PATHFINDER_BASE_URI
Also - remember - before deploying to prod, we have to tag the latest patroni image as 10 and test it. Would also be smart to tag the old image with something to keep it around for a while.
Oh - also - can you check with Kyubin what he wanted removed from the global config template while we're in there. We can remove the SPOTWX one.
| @@ -16,3 +16,7 @@ POSTGRES_PASSWORD="wps" | |||
| POSTGRES_DATABASE="wps" | |||
| POSTGRES_PORT="5432" | |||
| PORT="8080" | |||
| PATHFINDER_BASE_URI=https://console.pathfinder.gov.bc.ca:8443 | |||
| PROJECT_NAMESPACE=openshift_project_namespace | |||
There was a problem hiding this comment.
No need to add an env variable for this because we already keep track of this (check out openshift/scripts/oc_deploy.sh line 29)
…t faster, changed .sh files to use bash
…s into task/patroni_cluster_health/405
…bcgov/wps into task/patroni_cluster_health/405
…bcgov/wps into task/patroni_cluster_health/405
There was a problem hiding this comment.
Looks like PROJECT_NAMESPACE being in the ConfigMap hasn't been resolved but this can be dealt with later. As well as global.config.yml (am I seeing something different? ConfigMap and Secret applied in Openshift still don't match up with our template. I pointed out that bc-fire-weather-base-url, bc-fire-weather-user, bc-fire-weather-filter-id aren't in ConfigMap wps-api-global anymore rather they are in Secret wps-api-global )
|
Kudos, SonarCloud Quality Gate passed!
|
Updated health_check for Patroni cluster health. Outputs 'x out of y pods are healthy'
No description provided.