Default Tenant & Multi-Tenancy​Default ​Tenant & ​Multi-​Tenancy

Available on: Enterprise Edition

Release: 0.22.0

Default tenant is deprecated and multi-tenancy is enabled by default.

Overview

Multi-tenancy was introduced in Kestra 0.13. For backward compatibility with older versions (≤0.12), you could use the concept of a default tenant, which imitated the multitenancy feature with the so-called null-tenant or default tenant.

One and a half years later in Kestra 0.22, we are deprecating the default tenant functionality and plan to remove it in the future. We will provide enough time for the migration before removing the functionality and we'll publish a detailed migration guide for all customers who still use the default tenant so that they can migrate to the multi-tenancy feature.

How to keep the default tenant for now

To continue using the default tenant, set the defaultTenant configuration flag to true and tenants.enabled to false in your kestra.yml configuration file:

yaml
kestra:
  tenants:
    enabled: false
    defaultTenant: true

Note that in Kestra 0.22 and higher, defaultTenant is no longer enabled by default, so you must explicitly set that configuration option to true to keep using the default tenant.

Before 0.22.0

Here is the default multi-tenancy configuration before 0.22.0:

yaml
kestra:
  tenants:
    enabled: false
    defaultTenant: true

After 0.22.0

Here is the default multi-tenancy configuration after 0.22.0:

yaml
kestra:
  tenants:
    enabled: true
    defaultTenant: false

Was this page helpful?