sig-release-master-uprade-optional is now google-gke-upgrade #10965
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref: kubernetes/sig-release#347
Everything in sig-release-upgrade-optional was a GKE job. That means it's up to Google to watch, not SIG Release.
IMO the jobs themselves are more noise than they're worth if they're not being tended, but that is a PR for another day
I alpha-sorted the google dashboard list while I was at it
This reduces the dashboards CI signal needs to watch to:
/area release-team
/sig gcp
/sig release
FYI @mariantalla