Apply proxy config after hotfixes

[jcox10]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Currently the no_proxy configuration is reset after it is configured due to a duplicate self.no_proxy = None line being added in the autogenerated file configuration.py

Initially the thought was the script insert_proxy_config.sh was applying this duplicate. However, when this script is run on the openapi generated code, configuration.py looks correct.

Looking at the full release.sh script, there is another script applying proxy settings by cherry-picking commit 95a893c in apply-hotfixes.sh. This commit adds self.no_proxy = None. When applied after insert_proxy_config.sh this results in the duplicate lines and the no_proxy becoming None.

Changing the order of the applied scripts in release.sh so that insert_proxy_config.sh is run after apply-hotfixes.sh resolves the problem because insert_proxy_config.sh is able to detect the existing self.no_proxy = None and insert it's code correctly without resetting the no_proxy.

Which issue(s) this PR fixes:

Fixes #2460

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jcox10 / name: Jason Cox (2c5dd4b)

[k8s-ci-robot]

Welcome @jcox10!

It looks like this is your first PR to kubernetes-client/python 🎉. 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-client/python 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. 😃

[jcox10]

@roycaihw @yliaog Can you review this PR?

[yliaog]

/lgtm
/approve

thanks for the pr

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcox10, yliaog

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [yliaog]

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