Skip to content

Update Kube Versions for envtest-existing & kuttl PR Checks #4232

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

Conversation

andrewlecuyer
Copy link
Collaborator

Updates the min/max versions of Kubernetes used by the kubernetes-k3d and kuttl-k3d PR checks. This means PR checks for envtest-existing and kuttl tests are now run against the current min/max versions of Kubernetes supported by PGO according to the Supported Platforms page in the docs.

Checklist:

  • Have you added an explanation of what your changes do and why you'd like them to be included?
  • Have you updated or added documentation for the change, as applicable?
  • Have you tested your changes on all related environments with successful results, as applicable?
    • Have you added automated tests?

Type of Changes:

  • New feature
  • Bug fix
  • Documentation
  • Testing enhancement
  • Other

What is the current behavior (link to any open issues here)?

What is the new behavior (if this is a feature change)?

  • Breaking change (fix or feature that would cause existing functionality to change)

Other Information:

Updates the min/max versions of Kubernetes used by the kubernetes-k3d
and kuttl-k3d PR checks.  This means PR checks for envtest-existing and
kuttl tests are now run against the current min/max versions of Kubernetes
supported by PGO according to the Supported Platforms page in the docs.
@andrewlecuyer andrewlecuyer marked this pull request as ready for review August 5, 2025 23:08
@andrewlecuyer andrewlecuyer merged commit 470cfc8 into CrunchyData:main Aug 8, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants