feat: pass proxy configuration to operands

[miyunari]

jira: https://issues.redhat.com/browse/SECURESIGN-1038

[openshift-ci]

Hi @miyunari. Thanks for your PR.

I'm waiting for a securesign 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.

[lance]

/ok-to-test

[lance]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance, miyunari

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:

• OWNERS [lance]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[osmman]

/lgtm

[miyunari]

Hi @osmman - thanks for your review. Do you know what is going on with the ci pipeline tests?

[osmman]

Hi @osmman - thanks for your review. Do you know what is going on with the ci pipeline tests?

Hi, problem is that PR is from forked repository so Github action do not enable to access to CI's secrets. Current solution is to create new PR from current securesign/secure-sign-operator repo.

[miyunari]

Hi @osmman - thanks for your review. Do you know what is going on with the ci pipeline tests?

Hi, problem is that PR is from forked repository so Github action do not enable to access to CI's secrets. Current solution is to create new PR from current securesign/secure-sign-operator repo.

Ah ok, thanks for explaining @osmman 😃 Does this mean I have to create a new branch or can this be merged anyway? 🙂

[osmman]

Hi @osmman - thanks for your review. Do you know what is going on with the ci pipeline tests?

Hi, problem is that PR is from forked repository so Github action do not enable to access to CI's secrets. Current solution is to create new PR from current securesign/secure-sign-operator repo.

Ah ok, thanks for explaining @osmman 😃 Does this mean I have to create a new branch or can this be merged anyway? 🙂

Please create a new branch, Kind deployment and upgrade operator contains most of our e2e tests.

[miyunari]

Ok :)