Migration to Unified Gateway Deployment

Do this step before you migrate to v4.x of this component!

You have the following options to migrate to the unified gateway deployment:

  • Migrate with short service disruption

  • Migrate without service disruption

Migrate with Short Service Disruption

You dont have to do any migration steps, v4.x of this component will automatically migrate to the unified gateway deployment. If you have integrated this Mimir as datasource in Grafana, then the service name will change and you have to update your Grafana deployment.

Update the Grafana datasource url like following:

Old name: <instance_name>-nginx.<instance_namespace>.svc.cluster.local

New name: <instance_name>-gateway.<instance_namespace>.svc.cluster.local

Migrate without Service Disruption

This guide follows the official documentaton for the Migration to Unified Gateway Deployment.

Please read the official documentation about the migration before you continue.

Step 1: Enable Nginx Deployment

When upgrading to this version of the component, make sure you have nginx and gateway (default) enabled:

helm_values:
  gateway:
    enabled: true (1)
  nginx:
    enabled: true (2)
1 Enable the gateway deployment.
2 This should already be enabled.

Compile and push the catalog.

(Optional) Keep the old Service Name

If you want to migrate to the unified gateway deployment but want to keep the service name, you need to add the following configuration:

helm_values:
  gateway:
    service:
      nameOverride: mimir-nginx (1)
1 Overwrite the service name.

When you override the service name, use the correct name. The example above is only for illustration.

Step 2: Disable Nginx Deployment

In the first step we ensured the gateway deployment is present but not yet active, this makes sure the transition to the gateway deployment has the least disruption.

The nginx deployment will be removed, optionally keep the service name the same as before:

helm_values:
  gateway:
    enabled: true (1)
    ingress: ... (2)
    nginx:
      basicAuth: ... (3)
  nginx:
    enabled: false (4)
1 Keep the gateway configuration enabled.
2 Copy the ingress configuration from nginx.
3 Copy the basicAuth configuration from nginx.
4 Disable the nginx configuration.

Compile and push the catalog.