Realm deletion
Data Orchestrator v1.0 introduces the possibility of deleting a Realm, but currently devices which have a
valid certificate are not disconnected from the Realm. The issue is tracked
here.
Since publishing with devices on unexisting realms can cause problems (namely: RabbitMQ data queues filling up) which can also impact devices on other realms, a realm should be deleted only after ensuring that no devices are connected to it.
Due to the problems that realm deletion can cause, currently the feature must be explicitly enabled with a feature gate, i.e. by adding
features:
realmDeletion: true
components:
...
to the Data Orchestrator Custom Resource (which maps to setting the HOUSEKEEPING_ENABLE_REALM_DELETION
environment variable to true in the astarte_housekeeping container).
We also encourage avoiding to recreate realms with the same name to avoid having devices from the old realm reconnecting back to the new one.