-
Notifications
You must be signed in to change notification settings - Fork 111
fix bug where tokens can't refresh #94
base: master
Are you sure you want to change the base?
Conversation
What happens if you don't need a Trusted CA? Shouldn't this be optional? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this field should be optional
It also looks like we need a rebase here. |
fa65a8e
to
53046c1
Compare
da15cf0
to
8660cd7
Compare
8bdc98f
to
e840a9e
Compare
This field is effectively optional ... if its not provided the contents of the field in the kube config file or in the command line template will be an empty string which the kubeconfig config reader then ignores because its set to omit if empty in the kubeconfig object. |
Signed-off-by: Paul Czarkowski <[email protected]> Signed-off-by: Jignesh Sheth <[email protected]>
when tokens expire the kubeclient needs to refresh them and that means it needs to trust the CA of the openid server, to do that we need to pass `idp-certificate-authority-data` through to the kubeconfig. Signed-off-by: Paul Czarkowski <[email protected]> Signed-off-by: Jignesh Sheth <[email protected]>
Signed-off-by: Paul Czarkowski <[email protected]>
Signed-off-by: Paul Czarkowski <[email protected]>
Signed-off-by: Paul Czarkowski <[email protected]>
it would be great to get this merged in ... its blocking gangway from working with PKS |
related to #148 |
Same, we bump into this issue when the dex CA is a self-signed CA. |
any updates? |
Would love to see this merged as well, it's currently blocking us as well with using dex. |
when tokens expire the kubeclient needs to refresh them and that means
it needs to trust the CA of the openid server, to do that we need to
pass
idp-certificate-authority-data
through to the kubeconfig.