Upgrading the management plane

If you have previously deployed an earlier version of the Neutree management plane, refer to this section to upgrade it to version 1.2.0.

Deploying with Docker Compose

Download the version 1.2.0 control plane offline image.

Load the control plane offline images using the CLI tool.

Information:

If your environment has internet access, the system supports pulling container images from Docker Hub, so this step can be skipped.

Load the image to the local environment
Upload images to a remote registry

./neutree-cli-<arch> import controlplane \
  --package <controlplane_package> \
  --local

Parameter	Description
`<arch>`	The server’s CPU architecture: `amd64` or `arm64`.
`<controlplane_package>`	The control plane offline image name, in the format `neutree-controlplane-v1.2.0-enterprise-<arch>.tar.gz`.

./neutree-cli-<arch> import controlplane \
  --package <controlplane_package> \
  --mirror-registry <mirror_registry> \
  [--registry-project <registry_project>] \
  --registry-username <registry_username> \
  --registry-password <registry_password>

Parameter	Description
`<arch>`	The server’s CPU architecture: `amd64` or `arm64`.
`<controlplane_package>`	The control plane offline image name, in the format `neutree-controlplane-v1.2.0-enterprise-<arch>.tar.gz`.
`<mirror_registry>`	The registry address. Enter an OCI-compatible registry address without the `https://` prefix.
`[--registry-project <registry_project>]`	Optional. The project name in the registry. Ensure the corresponding project has been created in advance.
`<registry_username>`	The registry user’s username. The user must have permission to upload images.
`<registry_password>`	The registry user’s login password or access key (such as a token).

Using the parameters from the previous version management plane deployment, restart the control plane:
Terminal window
```
./neutree-cli-<arch> launch neutree-core \
  --version=v1.2.0-enterprise \
  --metrics-remote-write-url=http://<obstack_ip>:8480/insert/0/prometheus/ \
  --jwt-secret=<jwt_secret> \
  --grafana-url=http://<obstack_ip>:3030 \
  --admin-password=<admin_password>
```
Information:
When the control plane restarts, the system will automatically migrate the database. No manual intervention is required. Ensure that you use the same --jwt-secret parameter value as during the initial deployment.
Restart the monitoring components:
Terminal window
```
./neutree-cli-<arch> launch obs-stack
```
Check the running status of all services:
Terminal window
```
docker ps
```

Deploying with Kubernetes

Download the version 1.2.0 control plane offline image and the Helm Chart installation file.

Upload the control plane offline image to the Kubernetes cluster’s image registry using the CLI tool:

Information:

If your environment has internet access, the system supports pulling container images from Docker Hub, so this step can be skipped.

./neutree-cli-<arch> import controlplane \
  --package <controlplane_package> \
  --mirror-registry <mirror_registry> \
  [--registry-project <registry_project>] \
  --registry-username <registry_username> \
  --registry-password <registry_password>

Parameter	Description
`<arch>`	The server’s CPU architecture: `amd64` or `arm64`.
`<controlplane_package>`	The control plane offline image name, in the format `neutree-controlplane-v1.2.0-enterprise-<arch>.tar.gz`.
`<mirror_registry>`	The registry address. Enter an OCI-compatible registry address without the `https://` prefix.
`[--registry-project <registry_project>]`	Optional. The project name in the registry. Ensure the corresponding project has been created in advance.
`<registry_username>`	The registry user’s username. The user must have permission to upload images.
`<registry_password>`	The registry user’s login password or access key (such as a token).

Perform the Helm upgrade:
Terminal window
```
helm upgrade neutree neutree-v1.2.0-enterprise.tgz -f values.yaml \
  --namespace=neutree
```
Information:
The database migration will be performed automatically during the Helm upgrade. No manual intervention is required.
Check the Pod status:
Terminal window
```
kubectl get pods -n neutree
```