kubeseal is ignoring NO_PROXY variables upon request for cert.pem (403) about sealed-secrets HOT 6 CLOSED

Do you have the NO_PROXY variable set on your local environment? I assume you are using kubeseal from your local environment and not from inside the cluster, so kubeseal will get the proxy settings from your local environment.

from sealed-secrets.

It is set, however, the machine I'm on shouldn't be using the proxy at all..

The reason we shared the cluster info is that the same kubeseal client will work on one of our clusters but not on the one I'm posting about, so we figured it must be a difference in how the clusters are configured. However, when we look at the sealed-secrets-controller logs it looks like the kubeseal requests aren't even making it to the cluster because they're going through the proxy.

Super weird?

from sealed-secrets.

It is indeed weird, because I see two requests GET requests in your logs but the first one is succeeding, so it seems the NO_PROXY variable is functioning correctly there.

Can you try with an older version so we can see if there's something different? For example, 0.24.5.

from sealed-secrets.

yeah! it is weird, we saw the exact same thing, we're not sure why the second request is all of a sudden ignoring the NO_PROXY var.

We will give 0.24.5 a try, thanks!

from sealed-secrets.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

from sealed-secrets.

Due to the lack of activity in the last 7 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

from sealed-secrets.