Remove forseti-server ConfigMap

[kevensen]

Story

The forseti-security charts inject the contents of forseti_conf_server.yaml into a ConfigMap via the value of server.config.contents. This ConfigMap is then mounted inside the forseti-server container. This is done because previously, the forseti-server could only read forseti_conf_server.yaml locally. With the merge of forseti-security/forseti-security#3460, the forseti-server container can read the config file directly from GCS.

Proposal

If the server.config.contents is empty, read the forseti_conf_server.yaml file from GCS.

Validation

GIVEN server.config.contents has a value
WHEN Forseti on-GKE is deployed
THEN A ConfigMap is created and mounted in the forseti-server container

GIVEN server.config.contents has no value
WHEN Forseti on-GKE is deployed
THEN A ConfigMap is neither created nor mounted in the forseti-server container, and the forseti-server process reads the content from GCS.