chore: use subnet variables for no_proxy_hosts

[ludwig-mueller]

Description

no_proxy_host values were hardcoded to 10. network but users can specify custom subnets. Therefore, the custom subnets need to be used

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[BabithaPadiri]

LGTM

[surajsbharadwaj]

/run pipeline

[ludwig-mueller]

/run pipeline

[ludwig-mueller]

/run pipeline

[ludwig-mueller]

Rerunning since nlb creation failed. However, this test is expected to fail because the playbook values changed which will trigger a replace. Would like to see that error before merging.

[ludwig-mueller]

Force merging. Test ran as expected.