Resolve "Make oAuth2 Client data persistent"

Seems to work. I think this is okay as a workaround for now. Note that it creates One Pod with one container per application.

It doesn't require a lot of resources but maybe it is smarter to squeeze all the commands into one container?

@mark: Could you pls share more details what problem this MR solves ? Is there a related issue ? I don't understand why a cronjob is needed for data persitance.

assigned to @mark

unassigned @mark

assigned to @arie

There is huge overlap between the new cronjob and the one-off job that does the same, I guess you know that :-).

Perhaps my question is: how long do you think this workaround will have to stay in place? That would determine for me if we could invest a little time in DRYing it up.

assigned to @mark and unassigned @arie

resolved all threads

merged

mentioned in commit 551a026b