Does Mattermost operator on k8s interrupt mattermost service before upgrade of the database?

I read about Mattermost server upgrade in your documentation which says Mattermost needs to service interruption before database upgrade for the new app version, and then I watched your capture about Mattermost operator in Kubernetes, at 21:55, It says that Mattermost operator keeps serve and migrate, now I have a question: do a database migration does not need to service interruption? Does Mattermost operator in k8s can migrate DB on the new instance and serve traffic on the old instances at the same time?

Thanks in advance for your attention :slight_smile: