Convert acceptance matrix from KIND-binary to Kubernetes-version, parallelize in CI#56
Merged
Conversation
AbhiMgowda
force-pushed
the
Kind-matrix-improv
branch
from
65ff547 to
15daf9c
Compare
YashwanthaGowd
approved these changes
Jun 26, 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
2 participants
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.
Summary
The previous matrix iterated over downloaded KIND binaries, which didn't actually validate the chart against different Kubernetes API-server versions. This change pins each run to a specific kindest/node: so we exercise the chart on the K8s versions we claim to support, and runs them concurrently in CI.
Related
Checklist
I have documented a clear reason for, and description of, the change I am making.
Added/updated tests or validation steps (if applicable)
Verified local lint/validation
No breaking changes, or clearly documented
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.