Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

settings.network.no-proxy: describe the defaults more clearly #471

Open
larvacea opened this issue Jul 24, 2024 · 0 comments · May be fixed by #472
Open

settings.network.no-proxy: describe the defaults more clearly #471

larvacea opened this issue Jul 24, 2024 · 0 comments · May be fixed by #472

Comments

@larvacea
Copy link
Member

Path to page with content (do not include domain name):
en/os/1.20.x/api/settings/network/#no-proxy

What content is incorrect?

The no-proxy list automatically includes entries for localhost.

On Kubernetes variants (*-k8s-*) the no-proxy lists includes the Kubernetes API server endpoint as well as other commonly used Kubernetes DNS suffixes.

The example sets no-proxy entries for localhost.

The no-proxy list does contain the entries described here. These are never visible in apiclient, but are added to any entries from the API setting. Attempting to add no-proxy entries for localhost has no functional effect (Bottlerocket just ends up with no-proxy entries for localhost, twice).

What should the content say or communicate?
The content should include this behavior. Yes, bottlerocket will never proxy localhost, no, you can't override that behavior, and no, you will not see these automatic no-proxy entries in the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant