Option to handle dex-core client_secret via k8s secrets + alpine update

[VF-mbrauer]

Added functionality to overcome a security query where client_secretis in plain text inside the config.yaml, which is stored in a config map. So now it needs to be stored as a Base64 Encoded String and then the k8s-authenticator will decrypt internally and send the secret then towards the dexidp.

Also, the Alpine version has been increased as well as the documentation is updated for the client_secret change.

[VF-mbrauer]

@nabadger, I have changed the concept as of our last conversation in #179
So please review again and let me know if something is unclear.
Thanks a lot.

[VF-mbrauer]

@nabadger any news? Did you check already?

[VF-mbrauer]

@nabadger Is that repo still under maintainer mode? No answer since month already. So is here any chance to get an update? Otherwise we need to think of a product change as we need some support with the current one. Thanks a lot.

[VF-mbrauer]

• @nabadger PR is open since almost 4 month. Any chance to start working my PR?

[VF-mbrauer]

@nickmintel Can you please have a look? Thanks.

[nabadger]

@VF-mbrauer apologies - I've not been able to commit any time for this project recently (I'm not sure these circumstances will change either for a while).

After talking to internal team here, I've decided to raise a ticket to see if we can find other owners/maintainers of this project:

#194

[VF-mbrauer]

Hi @nabadger, fair point and I absolutely understand. So, no worries. Would be great if we could find other folks who take over as this product is great enrichment for the DEX-Core.