Conversation
|
LGTM label has been added. DetailsGit tree hash: 5d1fe77a124d44100bcb13786214fa380bd784e3 |
|
/retest |
|
/retest |
| cpu: 4 | ||
|
|
||
| - name: pull-kcp-operator-test-e2e-0.28 | ||
| - name: pull-kcp-operator-test-e2e-0.29 |
There was a problem hiding this comment.
Why are we dropping 0.28 tests?
The explicit 0.30 tests are now redundant, because the e2e-default is already on 0.30.
There was a problem hiding this comment.
0.28 is failing either way, as the cache server is not backported in there. And as code is using "current operator" codebase and just swaps images, it fails with "unknown flag"
@mjudeikis-bot create a follow-up issue so that canary tests would use the operator release image, not only swap image. it should test full operator upgrade, not just image
9e71ae4 to
fe1e0d1
Compare
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
@mjudeikis: The following test failed, say
DetailsInstructions 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. I understand the commands that are listed here. |
|
LGTM label has been added. DetailsGit tree hash: 050386d24884509f8c76f4a8508382623a7a5644 |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: ntnn The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/cherrypick release-0.5 |
|
@mjudeikis: #188 failed to apply on top of branch "release-0.4": DetailsIn response to this:
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. |
|
/cherry-pick release-0.5 |
|
@mjudeikis: #188 failed to apply on top of branch "release-0.4": DetailsIn response to this:
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. |
* bump kcp image * Add cache server cert support * drop 0.28 * add missing mount into shards * bump image * make PROTOKOL not fail CI
Summary
What Type of PR Is This?
Update kcp image
/kind chore
Related Issue(s)
Fixes #
Release Notes