#5701 [Core feature] Allow flyteadmin to start even if OIDC is unavailable (Improve flyteadmin startup resiliency) Issue created by ddl-rliu ### Motivation: Why do you think this is important? Today, the flyteadmin pod is blocked from starting up until the OIDC provider is healthy and available (the pod gets stuck in Error state). In some Kubernetes configurations, this erroring-pod could cause deployment-wide issues. The current behavior could be made more resilient. (Note that this applies to configurations using

useAuth=true

) ### Goal: What should the final outcome look like, ideally? A better approach in these configurations is to allow flyte to start up, even if the OIDC provider is unavailable. Then, try to re-initialize the OIDC provider later in the deployment lifespan. This is a more resilient approach, and it can be made configurable. ### Describe alternatives you've considered A workaround is to disable Flyte until the OIDC provider is available. ### Propose: Link/Inline OR Additional context Proposed fix here: #5702 ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte