Closed MattPOlson closed 3 years ago
I have the same issue, any update on this?
@maraku516 , have you tried setting up any authentication methods like the htpasswd or LDAP? The cluster's I have installed only marks AVAILABLE as true only after I setup a form of authentication other than the initial kubeadmin. https://docs.openshift.com/container-platform/4.3/authentication/identity_providers/configuring-htpasswd-identity-provider.html
https://10.6.202.40:6443/.well-known/oauth-authorization-server is served by the kube-apiserver, looks like there might be trouble rolling out the latest KAS config
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
/close
@stlaz: Closing this issue.
I'm setting up OpenShift 4.2 on vSphere, I have the cluster running and all the operators are running except the Authentication Operator. It's throwing the error below. I have 3 workers and two masters, and using HAProxy for my load balancer. I've verified it's configuration and all nodes are showing as healthy as available. I've also verified connectivity between all nodes. Details are below, please let me know if any more are needed.
I'm running this command to complete the install
This command works from all masters and workers