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
Bug 1895053: Verify builds can mount proxy trustedCA #25778
Bug 1895053: Verify builds can mount proxy trustedCA #25778
Conversation
|
@adambkaplan: This pull request references Bugzilla bug 1895093, which is invalid:
Comment In 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/test-infra repository. |
|
@adambkaplan: This pull request references Bugzilla bug 1895053, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In 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/test-infra repository. |
Verify builds can mount the cluster's custom PKI trust bundle if one is set on the cluster proxy configuration. When `mountProxyTrustedCA` is set to `true`, builds should add the container's trust bundle as a read-only mount. The custom PKI should be readable during the build execution, but should not be present in the resulting image.
771b6bf
to
bb06313
Compare
|
/bugzilla cc-qa |
|
@wewang58: This pull request references Bugzilla bug 1895053, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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/test-infra repository. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan, wewang58 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label qe-approved |
|
/refresh |
|
@bparees something seems to be up with this PR. It is waiting on the status of a job that has never run. ci/prow/e2e-metal-ipi-ovn-ipv6 |
|
/override ci/prow/e2e-metal-ipi-ovn-ipv6 |
|
@bparees: /override requires a failed status context to operate on.
Only the following contexts were expected:
In 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/test-infra repository. |
|
@openshift/openshift-team-developer-productivity-test-platform can you take a look at why this PR is stuck? it wants a job result for a context that doesn't seem to exist. we can manually merge it if need be, but i'd rather find a way to properly push it through. |
|
/test e2e-metal-ipi-ovn-ipv6 |
wait....that worked? why didn't the override work then? |
Override only works with a status that exists and that status didn't exist |
|
/retest |
|
@bparees I've submitted a pr to make the metal-ipi-ovn-ipv6 test optional. openshift/release#17679 |
|
/retest |
|
/override ci/prow/e2e-metal-ipi-ovn-ipv6 |
|
@bparees: Overrode contexts on behalf of bparees: ci/prow/e2e-metal-ipi-ovn-ipv6 In 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/test-infra repository. |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
14 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@adambkaplan: All pull requests linked via external trackers have merged:
Bugzilla bug 1895053 has been moved to the MODIFIED state. In 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/test-infra repository. |
Verify builds can mount the cluster's custom PKI trust bundle if one is
set on the cluster proxy configuration. When
mountProxyTrustedCAisset to
true, builds should add the container's trust bundle as aread-only mount. The custom PKI should be readable during the build
execution, but should not be present in the resulting image.