Comment 7 for bug 1892791

This bug is actually either back, or I screwed up testing of the fix earlier. I'm able to reproduce this on 2.8/stable.

After reviewing the code for dex-auth, the reason that the dex-auth charm uses uuid4() is to force a change in the pod-spec, which then forces dex-auth to reload its configuration with the updated version from disk. See here for the uuid call:

https://github.com/juju-solutions/bundle-kubeflow/blob/master/charms/dex-auth/reactive/dex_auth.py#L84

Without the call to uuid4(), Dex never gets updated configuration from the relation to oidc-gatekeeper.