Skip to content
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

Refine explanation of meeting regenerate after expiry requirement #28502

Merged
merged 1 commit into from Jan 5, 2024

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jan 5, 2024

Copy link
Contributor

openshift-ci bot commented Jan 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2024
To assert that a particular cert/key pair or CA bundle can do this, add the annotation to the secret or configmap.
```yaml
annotations:
certificates.openshift.io/auto-regenerate-after-offline-expiry: https//github.com/link/to/pr/adding/annotation, "quote escaped formatted name of e2e test that ensures the PKI artifact functions properly"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think just the test name should be sufficient, we can find out which PR added it with git blame (also across releases)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think just the test name should be sufficient, we can find out which PR added it with git blame (also across releases)

Based on past experience in kube with api approvals, there's nothing quite like the link embedded.

QE has required test every release that ensures the functionality works every release.
Links should be provided in the PR adding the annotation.
If you have not done this, you should not merge the annotation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you have not done this, you should not merge the annotation.
If you have not done this, you should not merge the PR setting this annotation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vrutkovs based on William's comment, I'm going to merge this to help us communicate where we're at with a perma-link.

I'm completely fine adding this extra verbiage, but I need to merge with green verifies.

@williamcaban
Copy link

The clarifications included in this PR for the generated document about how to meet the requirement provide the information PMs and Eng teams need to better understand what they need to do.

@deads2k
Copy link
Contributor Author

deads2k commented Jan 5, 2024

merging to allow linking for email/jira/etc.

@deads2k deads2k merged commit 544cbb0 into openshift:master Jan 5, 2024
7 of 22 checks passed
Copy link
Contributor

openshift-ci bot commented Jan 5, 2024

@deads2k: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node-upgrade 4b6e51b link false /test e2e-aws-ovn-single-node-upgrade

Full PR test history. Your PR dashboard.

Instructions 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/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202401052011.p0.g544cbb0.assembly.stream for distgit openshift-enterprise-tests.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants