Skip to content

Update kind images to include the Kubernetes 1.33 node image#7786

Merged
cert-manager-prow[bot] merged 3 commits intocert-manager:masterfrom
wallrj:update-kind-images
Jun 6, 2025
Merged

Update kind images to include the Kubernetes 1.33 node image#7786
cert-manager-prow[bot] merged 3 commits intocert-manager:masterfrom
wallrj:update-kind-images

Conversation

@wallrj
Copy link
Copy Markdown
Member

@wallrj wallrj commented Jun 6, 2025

This allows us to run the cert-manager E2E tests with Kubernetes 1.33, which is the latest version:

I'll also cherry pick this into release-1.18, because it is supposed to be supported and tested on K8S 1.33:

The images were updated automatically as follows:

# Find the version of Kind in use for cert-manager E2E tests
$ _bin/tools/kind version
kind v0.27.0 go1.23.6 linux/amd64

# Supply that version to the latest-kind-images.sh
$ ./hack/latest-kind-images.sh v0.27.0

I've added Kubernetes 1.33 as an optional test to the prow config in cert-manager/testing#1096

You can see the results of the test here:

Note: cert-manager doesn't yet use the kind module from makefile modules:

The images were last updated in #7526:

/kind cleanup

Update kind images to include the Kubernetes 1.33 node image

Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Use the latest-kind-images.sh script to get the latest Kind node images for the
version of Kind:

 $ _bin/tools/kind version
 kind v0.27.0 go1.23.6 linux/amd64

Signed-off-by: Richard Wall <richard.wall@cyberark.com>
@cert-manager-prow cert-manager-prow bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 6, 2025
@wallrj
Copy link
Copy Markdown
Member Author

wallrj commented Jun 6, 2025

/test pull-cert-manager-master-e2e-v1-33
/test pull-cert-manager-master-e2e-v1-33-upgrade

@wallrj
Copy link
Copy Markdown
Member Author

wallrj commented Jun 6, 2025

/test pull-cert-manager-master-e2e-v1-33-upgrade

@cert-manager-prow
Copy link
Copy Markdown
Contributor

@wallrj: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test pull-cert-manager-master-e2e-v1-32
/test pull-cert-manager-master-e2e-v1-32-upgrade
/test pull-cert-manager-master-make-test
/test pull-cert-manager-master-make-verify

The following commands are available to trigger optional jobs:

/test pull-cert-manager-master-e2e-v1-30
/test pull-cert-manager-master-e2e-v1-31
/test pull-cert-manager-master-e2e-v1-32-bestpractice-install
/test pull-cert-manager-master-e2e-v1-32-feature-gates-disabled
/test pull-cert-manager-master-e2e-v1-32-issuers-venafi-cloud
/test pull-cert-manager-master-e2e-v1-32-issuers-venafi-tpp
/test pull-cert-manager-master-e2e-v1-33
/test pull-cert-manager-master-license

Use /test all to run the following jobs that were automatically triggered:

pull-cert-manager-master-e2e-v1-32
pull-cert-manager-master-e2e-v1-32-upgrade
pull-cert-manager-master-make-test
pull-cert-manager-master-make-verify
Details

In response to this:

/test pull-cert-manager-master-e2e-v1-33-upgrade

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
Copy link
Copy Markdown
Member Author

wallrj commented Jun 6, 2025

/test pull-cert-manager-master-e2e-v1-32

Signed-off-by: Richard Wall <richard.wall@cyberark.com>
@wallrj
Copy link
Copy Markdown
Member Author

wallrj commented Jun 6, 2025

/test pull-cert-manager-master-e2e-v1-33

@wallrj wallrj changed the title WIP: Update kind images to include the Kubernetes 1.33 node image Update kind images to include the Kubernetes 1.33 node image Jun 6, 2025
@cert-manager-prow cert-manager-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 6, 2025
# limitations under the License.

# generated by "./hack/latest-kind-images.sh v0.26.0"
# generated by "./hack/latest-kind-images.sh v0.27.0"
Copy link
Copy Markdown
Member Author

@wallrj wallrj Jun 6, 2025

Choose a reason for hiding this comment

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

We've been using v0.26.0 kind node images with Kind v0.27.0 since kind was upgraded in #7669:

This won't happen if we use the Kind module from makefile-modules.

@wallrj
Copy link
Copy Markdown
Member Author

wallrj commented Jun 6, 2025

/cherry-pick release-1.18

@cert-manager-bot
Copy link
Copy Markdown
Contributor

@wallrj: once the present PR merges, I will cherry-pick it on top of release-1.18 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.18

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 requested a review from SgtCoDFish June 6, 2025 15:24
Copy link
Copy Markdown
Member

@SgtCoDFish SgtCoDFish left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

Seems good to me, cheers!

@cert-manager-prow
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SgtCoDFish

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

The pull request process is described here

Details 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 lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 6, 2025
@cert-manager-prow cert-manager-prow bot merged commit 5372509 into cert-manager:master Jun 6, 2025
7 checks passed
@wallrj wallrj deleted the update-kind-images branch June 6, 2025 16:04
@cert-manager-bot
Copy link
Copy Markdown
Contributor

@wallrj: new pull request created: #7787

Details

In response to this:

/cherry-pick release-1.18

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.

alexlebens pushed a commit to alexlebens/infrastructure that referenced this pull request Oct 8, 2025
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [cert-manager](https://cert-manager.io) ([source](https://github.com/cert-manager/cert-manager)) | minor | `v1.18.2` -> `v1.19.0` |

---

### Release Notes

<details>
<summary>cert-manager/cert-manager (cert-manager)</summary>

### [`v1.19.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.19.0)

[Compare Source](cert-manager/cert-manager@v1.18.2...v1.19.0)

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.

> 📖  Read the full release notes at cert-manager.io: <https://cert-manager.io/docs/releases/release-notes/release-notes-1.19>

Changes since `v1.18.0`:

#### Feature

- Add IPv6 rules to the default network policy ([#&#8203;7726](cert-manager/cert-manager#7726), [@&#8203;jcpunk](https://github.com/jcpunk))
- Add `global.nodeSelector` to helm chart to allow for a single `nodeSelector` to be set across all services. ([#&#8203;7818](cert-manager/cert-manager#7818), [@&#8203;StingRayZA](https://github.com/StingRayZA))
- Add a feature gate to default to Ingress `pathType` `Exact` in ACME HTTP01 Ingress challenge solvers. ([#&#8203;7795](cert-manager/cert-manager#7795), [@&#8203;sspreitzer](https://github.com/sspreitzer))
- Add generated `applyconfigurations` allowing clients to make type-safe server-side apply requests for cert-manager resources. ([#&#8203;7866](cert-manager/cert-manager#7866), [@&#8203;erikgb](https://github.com/erikgb))
- Added API defaults to issuer references group (cert-manager.io) and kind (Issuer). ([#&#8203;7414](cert-manager/cert-manager#7414), [@&#8203;erikgb](https://github.com/erikgb))
- Added `certmanager_certificate_challenge_status` Prometheus metric. ([#&#8203;7736](cert-manager/cert-manager#7736), [@&#8203;hjoshi123](https://github.com/hjoshi123))
- Added `protocol` field for `rfc2136` DNS01 provider ([#&#8203;7881](cert-manager/cert-manager#7881), [@&#8203;hjoshi123](https://github.com/hjoshi123))
- Added experimental field `hostUsers` flag to all pods. Not set by default. ([#&#8203;7973](cert-manager/cert-manager#7973), [@&#8203;hjoshi123](https://github.com/hjoshi123))
- Support configurable resource requests and limits for ACME HTTP01 solver pods through ClusterIssuer and Issuer specifications, allowing granular resource management that overrides global `--acme-http01-solver-resource-*` settings. ([#&#8203;7972](cert-manager/cert-manager#7972), [@&#8203;lunarwhite](https://github.com/lunarwhite))
- The `CAInjectorMerging` feature has been promoted to BETA and is now enabled by default ([#&#8203;8017](cert-manager/cert-manager#8017), [@&#8203;ThatsMrTalbot](https://github.com/ThatsMrTalbot))
- The controller, webhook and ca-injector now log their version and git commit on startup for easier debugging and support. ([#&#8203;8072](cert-manager/cert-manager#8072), [@&#8203;prasad89](https://github.com/prasad89))
- Updated `certificate` metrics to the collector approach. ([#&#8203;7856](cert-manager/cert-manager#7856), [@&#8203;hjoshi123](https://github.com/hjoshi123))

#### Bug or Regression

- ACME: Increased challenge authorization timeout to 2 minutes to fix `error waiting for authorization` ([#&#8203;7796](cert-manager/cert-manager#7796), [@&#8203;hjoshi123](https://github.com/hjoshi123))
- BUGFIX: permitted URI domains were incorrectly used to set the excluded URI domains in the CSR's name constraints ([#&#8203;7816](cert-manager/cert-manager#7816), [@&#8203;kinolaev](https://github.com/kinolaev))
- Enforced ACME HTTP-01 solver validation to properly reject configurations when multiple ingress options (`class`, `ingressClassName`, `name`) are specified simultaneously ([#&#8203;8021](cert-manager/cert-manager#8021), [@&#8203;lunarwhite](https://github.com/lunarwhite))
- Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities ([#&#8203;7961](cert-manager/cert-manager#7961), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish))
- Reverted adding the `global.rbac.disableHTTPChallengesRole` Helm option. ([#&#8203;7836](cert-manager/cert-manager#7836), [@&#8203;inteon](https://github.com/inteon))
- This change removes the `path` label of core ACME client metrics and will require users to update their monitoring dashboards and alerting rules if using those metrics. ([#&#8203;8109](cert-manager/cert-manager#8109), [@&#8203;mladen-rusev-cyberark](https://github.com/mladen-rusev-cyberark))
- Use the latest version of `ingress-nginx` in E2E tests to ensure compatibility ([#&#8203;7792](cert-manager/cert-manager#7792), [@&#8203;wallrj](https://github.com/wallrj))

#### Other (Cleanup or Flake)

- Helm: Fix naming template of `tokenrequest` RoleBinding resource to improve consistency ([#&#8203;7761](cert-manager/cert-manager#7761), [@&#8203;lunarwhite](https://github.com/lunarwhite))
- Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data ([#&#8203;7928](cert-manager/cert-manager#7928), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish))
- Major upgrade of Akamai SDK. NOTE: The new version has not been fully tested end-to-end due to the lack of cloud infrastructure. ([#&#8203;8003](cert-manager/cert-manager#8003), [@&#8203;hjoshi123](https://github.com/hjoshi123))
- Update kind images to include the Kubernetes 1.33 node image ([#&#8203;7786](cert-manager/cert-manager#7786), [@&#8203;wallrj](https://github.com/wallrj))
- Use `maps.Copy` for cleaner map handling ([#&#8203;8092](cert-manager/cert-manager#8092), [@&#8203;quantpoet](https://github.com/quantpoet))
- Vault: Migrate Vault E2E add-on tests from deprecated `vault-client-go` to the new `vault/api` client. ([#&#8203;8059](cert-manager/cert-manager#8059), [@&#8203;armagankaratosun](https://github.com/armagankaratosun))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMzUuNCIsInVwZGF0ZWRJblZlciI6IjQxLjEzNS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJjaGFydCJdfQ==-->

Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/1711
Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net>
Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>
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. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants