Deploying PostgreSQL for Mission Control
There are cases where you will want to use an external PostgreSQL and not the enclosed PostgreSQL. For more information, see Creating the Mission Control PostgreSQL Database.
This can be done with the following parameters.
...
--set postgresql.enabled=false \
--set database.url=${DB_URL} \
--set database.user=${DB_USER} \
--set database.password=${DB_PASSWORD} \
...Note
You must set postgresql.enabled=false for the chart to use the database.* parameters. Without it, they will be ignored.
Using Existing Secrets for PostgreSQL Connection Details
You can use existing secrets for managing the database connection details. Pass them to the install command with the following parameters.
export POSTGRES_USERNAME_SECRET_NAME=
export POSTGRES_USERNAME_SECRET_KEY=
export POSTGRES_PASSWORD_SECRET_NAME=
export POSTGRES_PASSWORD_SECRET_KEY=
...
--set database.secrets.user.name=${POSTGRES_USERNAME_SECRET_NAME} \
--set database.secrets.user.key=${POSTGRES_USERNAME_SECRET_KEY} \
--set database.secrets.password.name=${POSTGRES_PASSWORD_SECRET_NAME} \
--set database.secrets.password.key=${POSTGRES_PASSWORD_SECRET_KEY} \
...Deploying Elasticsearch for Mission Control
By default, the Mission Control Helm Chart deploys an Elasticsearch pod. It also configures Docker host kernel parameters using a privileged init container. In some installations, you may not be allowed to run privileged containers, in which case you can disable the Docker host configuration by configuring the following parameter.
--set elasticsearch.configureDockerHost=false
There are cases where you will want to use an external Elasticsearch and not the enclosed Elasticsearch.
This can be done with the following parameters.
--set elasticsearch.enabled=false \
--set elasticsearch.url=${ES_URL} \
--set elasticsearch.username=${ES_USERNAME} \
--set elasticsearch.password=${ES_PASSWORD} \