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

Setting HTTPS_PROXY requires NO_PROXY #1442

Open
ClusterJan opened this issue Oct 29, 2024 · 0 comments
Open

Setting HTTPS_PROXY requires NO_PROXY #1442

ClusterJan opened this issue Oct 29, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ClusterJan
Copy link

ClusterJan commented Oct 29, 2024

What is missing?

Setting an HTTPS_PROXY requires the NO_PROXY environment value to be set as well.
HTTPS_Proxy is used here

Why do we need it?

When the job is running in a cluster where an HTTP proxy is needed, the job isn't able to communicate to the Kubernetes API.
Have a look at the logs below.
In this example we ran the job manually with our proxy and the NO_PROXY set to 172.16.0.0/12.

Environment

  • K8ssandra Operator version:

    1.20.3

Anything else we need to know?:

  • Logs
2024/10/29 12:53:11 Upgrading CRDs to version 1.20.3
2024/10/29 12:53:11 Get "https://172.20.0.1:443/api?timeout=32s": Forbidden

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-284

@ClusterJan ClusterJan added the enhancement New feature or request label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant