Switch mongodb deployment from Hono helm chart to Bitnami chart

smaddis / smad-deploy-azure

Terraform scripts to set up AKS, ACR, KV for Kuksa Cloud (Eclipse Hono) deployment.

MIT License

0 stars 6 forks source link

Switch mongodb deployment from Hono helm chart to Bitnami chart #56

Closed JouHouFin closed 3 years ago

JouHouFin commented 3 years ago

Up to this point, we have deployed MongoDB via Hono helm chart, which has quite limited (or difficult) configuration options. Commit e7167dbfa1b643ffc5db3c575eabe7622c912448 switches MongoDB deployment to use the Bitnami MongoDB helm chart.

Tested to be working, but currently has rather basic configuration.

Linked to #38, but the question of data persistence is still open.

JouHouFin commented 3 years ago

Commit 802181df82ff05e0ce13786f578077143718ad61 switches to using set_sensitive when dealing with sensitive values.

JouHouFin commented 3 years ago

Commit 3c0b87e60e724fecf66ce3f2760ff01df170eb81:

switches to using mongo_values.yaml for non-sensitive values
adds a PersistentVolumeClaim named mongodb-data, that will use azure-disk-retain -StorageClass. This PVC is used by mongodb deployment.

In essence, #38 is fulfilled by this commit, but we we haven't tested if e.g. registered tenants are intact after bringing Hono down and up again.