Add option to set SSL_CERT_FILE for offline installation using custom CA for https proxy

[HappyFX]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Add option to pass in environment SSL_CERT_FILE to use custom CA https_proxy

Which issue(s) this PR fixes:

Fixes #10214

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add option to set `SSL_CERT_FILE` for offline installation using custom CA for https proxy

[k8s-ci-robot]

Welcome @HappyFX!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @HappyFX. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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/test-infra repository.

[linux-foundation-easycla]

• ❌ The email address for the commit (d4a276e) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[yankay]

/ok-to-test

[HappyFX]

Is it ok to add more verbosity in molecule tests with unsafe_show_logs: true?

[HappyFX]

@oomichi changed with suggestion https_proxy_cert_file

[HappyFX]

Have no idea why CI is failed on artefact push

[floryut]

@HappyFX Thank you for the PR, great desc/doc 🙇

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, HappyFX

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 [floryut]

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

[HappyFX]

All tests are passed. Can we merge or need some additional actions?

[yankay]

All tests are passed. Can we merge or need some additional actions?

Thanks @HappyFX

Nice PR!

Should the unsafe_show_logs be removed because it's not very useful as the default config,
And git squash the 14 git commits into 1.

[HappyFX]

@yankay ready

[yankay]

Thanks @HappyFX

/lgtm

[MrFreezeex]

/easycla

[linux-foundation-easycla]

• ❌ The email address for the commit (d4a276e) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[MrFreezeex]

@HappyFX Can you check that your commit email address match the one on your GitHub profile (by changing it in the commit or adding it in GitHub probably)?

[HappyFX]

changed commit email to github user and email
@MrFreezeex Now it's passed with EasyCLA

[MrFreezeex]

Thanks!
/lgtm