-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.13
-
None
-
Low
-
No
-
False
-
Description of problem:
After adding a custom authentication 'componentRoute' to the 'ingress.config.openshift.io' resource, the 'oauth-openshift-...' pods in the 'openshift-authentication' go into CrashLoopBackOff.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
Consistently
Steps to Reproduce:
1. Add a custom componentRoute for authentication in the ingress.config.openshift.io resource similar to the following: --- oc edit ingress.config.openshift.io cluster ... componentRoutes: - hostname: oauth.example.com name: oauth-openshift namespace: openshift-authentication servingCertKeyPairSecret: name: oauth-ssl2 ---
Actual results:
openshift-authentication pods go into CrashLoopBackOff
Expected results:
Custom change would successfully be rolled out to all dependent pods.
Additional info: