Closed slintes closed 12 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/cherry-pick release-0.6
don't merge it though yet, wait what we get downstream...
@slintes: once the present PR merges, I will cherry-pick it on top of release-0.6 in a new PR and assign it to you.
/test 4.13-e2e
@slintes: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test 4.12-ci-bundle-my-bundle
/test 4.12-images
/test 4.12-openshift-e2e
/test 4.12-test
/test 4.13-ci-bundle-my-bundle
/test 4.13-images
/test 4.13-openshift-e2e
/test 4.13-test
/test 4.14-ci-bundle-my-bundle
/test 4.14-images
/test 4.14-openshift-e2e
/test 4.14-test
/test 4.15-ci-bundle-my-bundle
/test 4.15-images
/test 4.15-openshift-e2e
/test 4.15-test
Use /test all
to run all jobs.
/test 4.13-openshift-e2e
/override e2e-k8s
@slintes: Overrode contexts on behalf of slintes: e2e-k8s
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: clobrano, slintes
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@slintes: new pull request created: #263
/cherry-pick release-0.4
@slintes: #262 failed to apply on top of branch "release-0.4":
Applying: Upgrade kube-rbac-proxy image to v0.15.0 and disable HTTP/2
Using index info to reconstruct a base tree...
M bundle/manifests/node-healthcheck-operator.clusterserviceversion.yaml
M config/default/manager_auth_proxy_patch.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/default/manager_auth_proxy_patch.yaml
CONFLICT (content): Merge conflict in config/default/manager_auth_proxy_patch.yaml
Auto-merging bundle/manifests/node-healthcheck-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/node-healthcheck-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Upgrade kube-rbac-proxy image to v0.15.0 and disable HTTP/2
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
The kube-rbac-proxy image was upgraded to version v0.15.0 in both manager_auth_proxy_patch.yaml and node-healthcheck-operator.clusterserviceversion.yaml. Additionally, a new argument was added to disable HTTP/2 to increase security levels following a recently discovered vulnerability.