nemerosa / ontrack-chart Goto Github PK

In the deployment template, use the configurable service names for the URLs of Postgresql and Elasticsearch

Document how Casc secrets can be mapped. Make the Casc secret mode = file configurable.

Can be done once nemerosa/ontrack#954 is released.

Ontrack displays the following message:

request [GET http://ontrack-search-headless:9200/_cluster/health/] returned 1 warn │ │
│ ings: [299 Elasticsearch-7.14.0-dd5a0a2acaa2045ff9624f3729fc8a6f40835aa1 "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be a │ │
│ ccessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.14/security-minimal-setup.html to enable security."]

Allow the configuration of arbitrary environment variables for the Ontrack container.

Referring to a config map whose keys contain Casc files.

By default, the chart relies on a local PG dependency for the database. Setup the chart and document the setup to use an external database.

Upon reinstallation, RabbitMQ will fail because credentials are stored in the PVC and will prevent the credentials to be changed (even if they are identical).

Alternative would be to preemptively create a secret and tell the RabbitMQ chart that the secret is provided.

Check which 11 version is available in Bitnami and how the configuration has changed.

While it's possible to set annotations to all the container in the Ontrack pod (Ontrack + any extra container), we can also wish to have annotations ONLY for the Ontrack container.