Configuration

Magnum UI specific settings

CLUSTER_TEMPLATE_GROUP_FILTERS

Added in version 5.3.0: (Ussuri)

Default: None

Examples:

CLUSTER_TEMPLATE_GROUP_FILTERS = {
    "dev": ".*-dev-.*",
    "prod": ".*-prod-.*"
}

The settings expects a dictionary of group name, to group regex.

When set allows a cloud provider to specify template groups for their cluster templates based on their naming convention. This helps limit users from upgrading their cluster to an invalid template that will not work based on their current template type.

This filtering is only relevant when choosing a new template for upgrading a cluster.

MAGNUM_INGRESS_CONTROLLERS

Added in version 5.3.0: (Ussuri)

Default: None

Examples:

MAGNUM_INGRESS_CONTROLLERS = [
    {
        "name": "NGINX",
        "labels": {
            "ingress_controller": "nginx"
        }
    },
    {
        "name": "Traefik",
        "labels": {
            "ingress_controller": "traefik"
        }
    },
    {
        "name": "Octavia",
        "labels": {
            "ingress_controller": "octavia"
        }
    }
]

This setting specifies which Kubernetes Ingress Controllers are supported by the deployed version of magnum and map directly to the response returned by the magnum-ui api/container-infra/ingress_controllers endpoint.

MAGNUM_AVAILABLE_ADDONS

Added in version 5.3.0: (Ussuri)

Default: None

Examples:

MAGNUM_AVAILABLE_ADDONS = [
    {
        "name": "Kubernetes Dashboard",
        "selected": True,
        "labels": {
            "kube_dashboard_enabled": True
        }
    },
    {
        "name": "Influx Grafana Dashboard",
        "selected": False,
        "labels": {
            "influx_grafana_dashboard_enabled": True
        }
    }
]

Specifies which ‘Addon Software’ is available or supported in the deployed version of magnum and specifies which labels need to be included in order to enable or disable the Software Addon.

Examples of Addon Software include but are not limited to:

Values specified in the MAGNUM_AVAILABLE_ADDONS setting map directly to the values returned in the response of the api/container-infra/available_addons endpoint.

MAGNUM_MINIMUM_FLAVOR_RAM

Added in version 16.0.0: (2026.1 Gazpacho)

Default: 2048

Examples:

MAGNUM_MINIMUM_FLAVOR_RAM = 4096

Specifies the minimum RAM (in MiB) required to run a Kubernetes node.

This is used as a filter when displaying compute flavors in the dashboard. Applies to both worker and control plane nodes.

MAGNUM_MINIMUM_FLAVOR_VCPU

Added in version 16.0.0: (2026.1 Gazpacho)

Default: 2

Examples:

MAGNUM_MINIMUM_FLAVOR_VCPU = 4

Specifies the minimum number of vCPU required to run a Kubernetes node.

This value is used as a filter when displaying compute flavors in the dashboard. Applies to both worker and control plane nodes.

Horizon Settings

For more configurations, see Configuration Guide in the Horizon documentation.