You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 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.
The text was updated successfully, but these errors were encountered: