-
Notifications
You must be signed in to change notification settings - Fork 1k
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
fix(gcp): Relaxed health check for GCP accounts #6200
Conversation
Ideally this gets changed a bit in the future. With the Bean, it would disable the thread & scheduled job which would output a log message every 30 seconds. Since it was also a component that Bean disable didn't help this. Doing this method, we still get the log message, the scheduled run that outputs the log message every 30 seconds, plus the whole if check thing. It's MINOR but... we shouldn't really load these health checks this way. Be good to fix all of them to disable them vs. the current implementation. |
@Mergifyio backport release-1.28.x |
✅ Backports have been created
|
@Mergifyio backport release-1.34.x release-1.33.x release-1.32.x |
✅ Backports have been created
|
(cherry picked from commit 28599eb) # Conflicts: # clouddriver-google/src/main/groovy/com/netflix/spinnaker/clouddriver/google/health/GoogleHealthIndicator.groovy
(cherry picked from commit 28599eb)
(cherry picked from commit 28599eb)
(cherry picked from commit 28599eb)
* fix(gcp): Relaxed health check for GCP accounts (#6200) (cherry picked from commit 28599eb) # Conflicts: # clouddriver-google/src/main/groovy/com/netflix/spinnaker/clouddriver/google/health/GoogleHealthIndicator.groovy * fix: Fixes PR to match 1.28 versions of credential repository APIs --------- Co-authored-by: Christos Arvanitis <christos.arvanitis@armory.io> Co-authored-by: Jason McIntosh <jason.mcintosh@harness.io>
…nnaker#6203) (cherry picked from commit 28599eb) Co-authored-by: Christos Arvanitis <christos.arvanitis@armory.io>
The majority of cloud providers (AWS, K8s) and dockerRegistry have already implementations for relaxed health checks via a configuration property in the respective provider block.
On GCP provider though it was attempted to be addressed by #6093 which however was not the correct implementation since the Health check is registered in initialisation and it is a scheduled task.
This PR fixes the issue spinnaker/spinnaker#3923 for the GCP provider