Skip to content

Setup tests for release-1.18 #1095

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

Merged
merged 5 commits into from
Jun 6, 2025

Conversation

wallrj
Copy link
Member

@wallrj wallrj commented Jun 6, 2025

Based on the same changes for release-1.17 (#1074) and release-1.16 (#1061)

As described in the section "Proceed to the post-release "testing and release" steps:" in https://cert-manager.io/docs/contributing/release-process/#minor-releases

In a follow up PR I will add testing for Kubernetes 1.33

Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
@cert-manager-prow cert-manager-prow bot added dco-signoff: no Indicates that at least one commit in this pull request is missing the DCO sign-off message. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 6, 2025
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
@cert-manager-prow cert-manager-prow bot added dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. and removed dco-signoff: no Indicates that at least one commit in this pull request is missing the DCO sign-off message. labels Jun 6, 2025
@wallrj wallrj requested a review from inteon June 6, 2025 13:29
@inteon
Copy link
Member

inteon commented Jun 6, 2025

/approve
/lgtm

@cert-manager-prow cert-manager-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2025
@cert-manager-prow
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon

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

@cert-manager-prow cert-manager-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 6, 2025
@cert-manager-prow cert-manager-prow bot merged commit 76c8892 into cert-manager:master Jun 6, 2025
6 checks passed
@cert-manager-prow
Copy link
Contributor

@wallrj: Updated the following 3 configmaps:

  • plugins configmap in namespace default at cluster default using the following files:
    • key plugins.yaml using file config/plugins.yaml
  • config configmap in namespace default at cluster default using the following files:
    • key config.yaml using file config/config.yaml
  • job-config configmap in namespace default at cluster default using the following files:
    • key cert-manager-release-1.18.yaml using file config/jobs/cert-manager/cert-manager/release-1.18/cert-manager-release-1.18.yaml

In response to this:

Based on the same changes for release-1.17 (#1074) and release-1.16 (#1061)

As described in the section "Proceed to the post-release "testing and release" steps:" in https://cert-manager.io/docs/contributing/release-process/#minor-releases

In a follow up PR I will add testing for Kubernetes 1.33

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-sigs/prow repository.

@wallrj wallrj deleted the release-1.18 branch June 6, 2025 13:32
Copy link
Member Author

Choose a reason for hiding this comment

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

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. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants