jobs: pin release-informing node jobs away from k8s-jkns-ci-node-e2e #17264
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.
release-blocking jobs were already moved to a different GCP project in #17251 and #17257 due to network issues. This also moves the release-informing jobs away until new GCP project is created (ref: kubernetes/kubernetes#89892 (comment)).
Signed-off-by: hasheddan georgedanielmangum@gmail.com
Ref: kubernetes/kubernetes#89893
@spiffxp if you don't think this is necessary feel free to close this. However, it would be helpful from a CI Signal perspective for us to be getting more accurate signal from these release-informing tests in the short-term.
/cc @spiffxp @dims @kubernetes/ci-signal