> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-4-2/deployment/upgrading-connectware/on-kubernetes/to-1-7-0-on-kubernetes.md).

# Upgrading Connectware to 1.7.0 (Kubernetes)

Connectware 1.7.0 affects the backward compatibility of the Connectware broker. Older broker data volumes are not compatible with brokers of Connectware 1.7.0 and newer. Upgrading to Connectware 1.7.0 requires additional upgrade procedures.

Additionally, multi-factor authentication (MFA) is now controlled via a dedicated configuration switch.

{% hint style="warning" %}

## Check your upgrade path

This upgrade is one step of a longer upgrade path. Before you continue, check [Connectware Upgrade Paths](/2-4-2/deployment/upgrading-connectware/upgrade-paths.md) to determine which steps apply to your installation.
{% endhint %}

## Important Notes

This upgrade will delete all persisted data of the Connectware broker. This includes client sessions, subscriptions, and retained data. If your configuration relies on any type of data persisted by the broker, make sure to properly initialize your applications after the upgrade.

If you rely on persisted data, create a backup or snapshot of the broker data volumes. This allows you to roll back in case of complications.

## Upgrading Procedure

Here are the complete instructions for upgrading your Connectware installation to version 1.7.0.

1. Scale down the broker cluster in Kubernetes. Set the number of broker nodes and control-plane-broker nodes to zero and wait until all broker pods have been successfully removed.
2. Delete the broker and control-plane-broker data volumes. Log volumes do not have to be deleted.
3. If you are using multi-factor authentication (MFA), set the Helm value `global.authentication.mfa.enabled` to `true`.
4. Apply the updated Helm chart of Connectware version 1.7.0 For more information, see [Installing Connectware on Kubernetes](/2-4-2/deployment/installing-connectware/on-kubernetes.md).

Once all pods are up and running again and no new deviations appear in Connectware, the upgrade has been successful.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybus.io/2-4-2/deployment/upgrading-connectware/on-kubernetes/to-1-7-0-on-kubernetes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.