Replies: 3 comments
-
Hmmm, thanks but from the proxy there is no way back to the okd Cluster:
And does what, imho nothing? Because I see all other nodes, worker and master, to use the proxy in the correct way. But the auth provider is getting an 503 from the proxy when calling the "oauth-openshift.apps.yy.okd.example.com". I hope this is not a problem some time in a future release :( Thanks for the hint, |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks 😄 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We recently deployed a Proxy to our cluster and everything works fine, except one little thing. One of the master nodes tries to reach the following oauth Url using the Proxy. But we excluded the Url in the noProxy setting.
For whatever reason we see in the proxy logs the following Connect:
Fyi we use squid. This shouldn't be happening in my opinion, because of the noProxy Setting
Version: 4.12.0-0.okd-2023-04-16-041331
We have this behavior on all our clusters with the same Version
Why is this happening? Any thoughts on this?
Regards Philipp
Beta Was this translation helpful? Give feedback.
All reactions