Conversation
daynewlee
approved these changes
Feb 3, 2026
|
@dcaravel: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Contributor
Author
|
Latest test failure is a good thing, it shows tests are now running but failed due to data changes. Going to merge this one and create another PR for updating the individual failing test. |
dcaravel
added a commit
that referenced
this pull request
Feb 4, 2026
dcaravel
added a commit
that referenced
this pull request
Feb 6, 2026
dcaravel
added a commit
that referenced
this pull request
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates the Scanner CI certs, this must be done 'yearly'
Scanner OSCI jobs have been failing / timing out waiting for scanner pods to be ready, the pods will never become ready due to invalid certs (example):
The certs were updated by following the instructions in
scripts/cert/README.mdAdditionally the
gen-cert.shscript was deleting the Konfluxrpms.in.yamlandrpms.lock.yamlfiles in the root of the scanner repo, the script was adjusted to no longer delete those files.Last time certs were updated was here: #1748
Those certs had the expiration:
The new certs have the following expirations: