Jason Parraga
We have an implementation of this internally that we could potentially upstream.
> [@Sovietaced](https://github.com/Sovietaced) coming back to this, it'd be a great contribution too Looking at our implementation it looks like we built a separate cloud event notification processor and build our...
Can you run `make generate` in `flyteidl` dir and `make lint-fix` in `flyteadmin` dir? There are some build failures
We have an end to end test currently validating this functionality and it seems like there might be a correctness error in the logic that looks for previous executions. ```go...
> Makes sense - this change will increase `ResourceExhausted` errors noticeably, especially if measured as a metric and it can be misleading since it isn't really an error. Some changes...
@EngHabu seemed happy with this. We've been using a variation of it in production for the past couple weeks so I think its safe to land this.
> 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...
> @Sovietaced , can you point to this change? Are you thinking of #5621? Yeah I think so
I feel that it is fairly normal for clients to cache oauth metadata. That is something I'd be happy to work on as I've done it before.
Does anyone have an MVP flyte-binary `values.yaml` that can reproduce this issue?