How to Upgrade

In order to upgrade Mia-Platform Console, all you need to do is to update the mia-console Chart version dependency in your Chart.yaml file.

caution

when upgrading Mia-Platform Console to a new major release, always remember that updates must be performed one major at a time. Therefore, in order to upgrade from v9 to v11 you must first upgrade to v10.

Chart.yaml

apiVersion: v2
name: console
version: "0.0.0"
kubeVersion: ">= 1.20.0-0"
description: Self Hosted Console Installation Chart
type: application
dependencies:
  - name: mia-console
    version: "X.Y.Z"
    repository: "https://nexus.mia-platform.eu/repository/helm-internal/"

When upgrading also make sure to check if any new configuration option is available or if something has been removed.

info

The Chart version follows semver policy so any breaking change with the Chart will always be followed by a Major release. Minor releases may include new configuration options while as a general rule of thumb, patches never holds new configuration options but only internal updates and fixes.

v11 - version upgrades

Upgrade from v11.5.x to v11.6.0

This version introduces the possibility to create Jobs from CronJobs, and to delete Jobs.

Therefore, the Kubernetes Service Account set up on the clusters managed by your Console instance needs some specific permissions.

If during the Cluster Preparation you chose the Automatic procedure, just make sure that you have been provided at least the v2.18.0 Mia-Platform Helm Chart.

Otherwise, if you manually configure your cluster connections, in the ClusterRole bound to the Console Kubernetes Service Account, add the create and delete verbs to the jobs resource, along with the already present get and list:

- apiGroups:
      - "batch"
    resources:
      - "jobs"
    verbs:
      - "get"
      - "list"
      - "create"
      - "delete"

Upgrade from v11.4.0 to v11.4.1

With version v11.4.1 (Chart version v9.5.0) the feature toggle service now uses Rönd, therefore rbacSidecar configurations should be added:

featureToggleService:
  deploy:
    # ...
  rbacSidecar:
    resources:
      requests:
        memory: "100Mi"
        cpu: "100m"
      limits:
        memory: "200Mi"
        cpu: "200m"

Upgrade from v11.3.0 to v11.4.0

With version v11.4.0 (Chart version v9.4.0) a new service has been added, make sure to configure resource requirements and HPA according to your installation for exportService

exportService:
  deploy:
    resources:
      requests:
        memory: "200Mi"
        cpu: "50m"
      limits:
        memory: "500Mi"
        cpu: "350m"
    hpa:
      annotations: {}
      minReplicas: 2
      maxReplicas: 4
      targetCPUUtilizationPercentage: 70
  podDisruptionBudget:
    enabled: true
    minAvailable: 1

Furthermore, configurations.exportServiceHostname value is removed. So, you can remove it from your values file.

Upgrade from v11.2.1 to v11.3.0

With version v11.3.0 (Chart version v9.3.0) a new service has been added, make sure to configure resource requirements and HPA according to your installation for eventsManager

eventsManager:
  deploy:
    resources:
      requests:
        memory: "50Mi"
        cpu: "50m"
      limits:
        memory: "250Mi"
        cpu: "350m"
    hpa:
      annotations: {}
      minReplicas: 2
      maxReplicas: 4
      targetCPUUtilizationPercentage: 70
  rbacSidecar:
    resources:
      requests:
        memory: "100Mi"
        cpu: "100m"
      limits:
        memory: "300Mi"
        cpu: "300m"
  podDisruptionBudget:
    enabled: true
    minAvailable: 1

Upgrade from v10.9.0 to v11.2.1

Between v10.9.0 (Chart version v9.0.15) and v11.2.1 (Chart version v9.2.1) the are no notable changes to take care of.