test-infra
test-infra copied to clipboard
feat: Add tests with higher version skew for compatibility version
Now that the alpha.1 tag has been cut for K8s, we have had emulated version added for 3 releases. Add tests for that use case as the KEP states that we should be able to support up to N-3 version skew for emulated versions.
Hi @michaelasp. Thanks for your PR.
I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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.
/cc @aaron-prindle /cc @BenTheElder
/cc @Jefftree
/ok-to-test
/hold /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: BenTheElder, michaelasp
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~config/OWNERS~~ [BenTheElder]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/unhold
@michaelasp: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:
- key
compatibility-versions-e2e.yamlusing fileconfig/jobs/kubernetes/sig-testing/compatibility-versions-e2e.yaml
In response to this:
Now that the
alpha.1tag has been cut for K8s, we have had emulated version added for 3 releases. Add tests for that use case as the KEP states that we should be able to support up to N-3 version skew for emulated versions.
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.