cancel
Showing results for 
Search instead for 
Did you mean: 
MikeInAZ
Flight Engineer
Flight Engineer
  • 374 Views

Waiting 3 mins after IDM change

Jump to solution

Is there a way to force an immediate pod refresh of the openshift-authentication namespace instead of waiting 3 mins after a replace of the oauth.yaml?

1 Solution

Accepted Solutions
Chetan_Tiwary_
Community Manager
Community Manager
  • 362 Views

@MikeInAZ cluster wide authentication pods will take some time to refresh. 5+ mins is generally epxected but surely depends upon the infrastructure.

Sometimes, it gets ready for me in 3 mins :

Chetan_Tiwary__0-1727289668805.png

 

View solution in original post

3 Replies
Chetan_Tiwary_
Community Manager
Community Manager
  • 363 Views

@MikeInAZ cluster wide authentication pods will take some time to refresh. 5+ mins is generally epxected but surely depends upon the infrastructure.

Sometimes, it gets ready for me in 3 mins :

Chetan_Tiwary__0-1727289668805.png

 

akhmadkun
Cadet
Cadet
  • 348 Views

You could try deleting the pod on the openshift-authentication namespace, openshift will then recreate the pod with the new oauth

MikeInAZ
Flight Engineer
Flight Engineer
  • 331 Views

Yep, i was curious about the same with doing just that as shown below. It should recreate after,

$ oc delete pod -n openshift-auththentication -l app=authentication

0 Kudos
Join the discussion
You must log in to join this conversation.