How is DQ now using a Secret instead of ENV Vars Configmap with K8s Docker?

Question: How is DQ now using a Secret instead of ENV Vars Configmap?
Answer: from Brian Mearns:
The following Env Vars are now managed as a Secret instead of as a Configmap, for K8s Docker only:

LICENSE_KEYLIVY_SSL_KEY_PASSSERVER_SSL_KEY_PASSSPRING_AGENT_DATASOURCE_PASSWORDSPRING_AGENT_DATASOURCE_USERNAMESPRING_DATASOURCE_PASSWORDSPRING_DATASOURCE_USERNAME

To be clear, they will still need to make sure that the user with view to the cluster does not have access to secrets or the ability to bash into a pod where those secrets are mounted and used. Metastore password should also still be encrypted using the CLI utility we provide.

BigDataBear

Posted 4 years ago · Edited 1 year ago

0 comments

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard