https://git.k8s.io/community/contributors/guide/first-contribution.md" rel="nofollow">https://git.k8s.io/community/contributors/guide/first-contribution.md and developer guide https://git.k8s.io/community/contributors/devel/development.md 2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label 3. Ensure you have added or ran the appropriate tests for your PR: https://git.k8s.io/community/contributors/devel/sig-testing/testing.md 4. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews 5. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md 6. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests --> **What type of PR is this?** /kind feature **What this PR does / why we need it**: sets kube CIDR's in No_proxy environment **Which issue(s) this PR fixes**:  Fixes kubernetes-sigs#8864 **Special notes for your reviewer**: the default configuration does not include no_proxy settings if one uses default config and sets proxy setting pods cannot connect to API service PS it's my first time creating an PR i'll include my code below **Does this PR introduce a user-facing change?**:  ```release-note NONE ``` **roles/kubespray-defaults/defaults/main.yaml** `no_proxy: "{{ no_proxy | default ('{{ kube_service_addresses }},{{ kube_pods_subnet }},{{ cluster_name }}') }}" ` `NO_PROXY: "{{ no_proxy | default ('{{ kube_service_addresses }},{{ kube_pods_subnet }},{{ cluster_name }}') }}"` **inventory/sample/group_vars/all/all.yml** `##Refer to roles/kubespray-defaults/defaults/main.yml before modifying no_proxy` `##Make sure you add kube_service_addresses, kube_pods_subnet and cluster_name below or pods cannot connect to API service` `no_proxy: "{{ kube_service_addresses }}, {{ kube_pods_subnet }}, {{ cluster_name }}"`

Commits

Commits on Jun 6, 2022

adds required no_proxy setting