Using Mattermost Operator Functionality¶
The Mattermost Kubernetes Operator supports rolling upgrades so you can upgrade your Mattermost deployment with zero downtime. This process requires at least two replicas as a rolling upgrade cannot be performed if there is only one pod. Replicas are created when a user count is selected and exceeds 100.
New Mattermost releases are announced via our community server, as well as social media and email.
Performing rolling upgrades
- Log in to your Kubernetes instance.
- Open the
mattermost-installation.yamlmanifest (the one created during installation).
- Update the
spec.versionvalue to the new version.
- Save the changes.
Apply the changes with
$ kubectl apply -n mattermost -f [PATH_TO_MATTERMOST_MANIFEST]
The operator initiates a job in the Kubernetes cluster and once migration is complete the pods are restarted. If necessary, a database migration is also performed.
To view information about the running job, use
$ kubectl -n mattermost get jobs
At least one pod is available at all times and once all pods are restarted with the new version the upgrade is complete.
To view the status of the pods and to confirm their state, use
$ kubectl -n mattermost get pods
The STATUS of the pods should be running/ready, with an AGE of 10-15 seconds.