Integrate kibana with google auth

changed the description

Outstanding issue: the ES pods do not appear to restart when new SSO values are applied. The logging/logging-ek-es-master-es-config secret is updated correctly, but that doesn't cause the pods to restart and the changes aren't automatically applied which can cause discrepancies between the Kibana login UI and the active ES SSO configuration.

There is a similar (or identical?) issue on the es/kb repo side which may not be critical to resolve... but this one probably needs to be. When we update the SSO provider values through bb, that should be propagated out to runtime.

I tried adding a checksum annotation to the HR as follows, but I'm not sure that was that was the correct file/object to track:

annotations:
    checksum/values: {{ include (print $.Template.BasePath "/logging/elasticsearch-kibana/values.yaml") . | sha256sum }}

Definitely open to suggestions on this one..

added 102 commits

d7538cae...a797969b - 101 commits from branch master
3d9579f0 - Merge branch 'master' into feature/361-integrate-kibana-with-google-auth

Compare with previous version

added 1 commit

046d6208 - Updated elasticsearch values to nil check optional SSO fields to prevent...

Compare with previous version

added 3 commits

a23b5f91 - Added 'requested_scopes' list as an overridable value.
ec26f45d - Updated google-auth-examples with new field
1d602e8d - Added unused claim_group back as an 'ignored value'. Need to add a note about...

Compare with previous version