
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 682 Views
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?
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 670 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 :

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 671 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 :

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 656 Views
You could try deleting the pod on the openshift-authentication namespace, openshift will then recreate the pod with the new oauth

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 639 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