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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added allow_proxy option (default: false) for enabling or disabling the use of a proxy for the k8s_metadata_decorator operator.
Generally, you would not want to use a proxy for connections to the Kubernetes API, however, the Kubernetes client will use any proxy set at HTTP_PROXY or HTTPS_PROXY unless the proxy function is set.
This is a problem because the proxy is likely not inside the cluster, therefore it cannot forward requests to the internal Kubernetes APIs.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
Added
allow_proxy
option (default: false) for enabling or disabling the use of a proxy for the k8s_metadata_decorator operator.Generally, you would not want to use a proxy for connections to the Kubernetes API, however, the Kubernetes client will use any proxy set at HTTP_PROXY or HTTPS_PROXY unless the proxy function is set.
This is a problem because the proxy is likely not inside the cluster, therefore it cannot forward requests to the internal Kubernetes APIs.
supporting docs:
More context here: resolves #238
Please check that the PR fulfills these requirements