Closed RomanGz closed 4 years ago
I should add that we have other apps like kubernetes dash working fine authenticating against the same dex oidc.
Figured it out. Didn't realize Rancher "api" wasn't a direct path to kube api, and had its own auth proxy in front of it.. Once I exposed & connected directly to the kube api, all worked well.
All works well as far as generating the config goes, however, kubectl fails with:
Generated config:
^ That CA looks like the internal cert. Should it be something else? Replacing it with GoDaddy CA results in 401 unauthorized on kubectl calls
SSL on api server passes any other SSL checks. Not sure where the chain is broken as this issue only seems common with self-signed certs.