Updating the control plane images

For Neutree versions with severe issues, a control plane image of the same version might be released to quickly resolve validation issues. If you have already upgraded to the affected version, first download and upload the new control plane image from the image registry or the internal file server. Then, forcibly update neutree-core and neutree-api to the latest versions according to your deployment method. Other materials can be reused without downloading them again.

Kubernetes deployment

1. Trigger Kubernetes to pull the latest images again:

   kubectl -n neutree patch deployment neutree-core neutree-api --type=json \
     -p='[{"op":"replace","path":"/spec/template/spec/containers/0/imagePullPolicy","value":"Always"}]'

2. Confirm that the update is complete:

   kubectl -n neutree rollout status deployment/neutree-core --timeout=10m
   kubectl -n neutree rollout status deployment/neutree-api --timeout=10m

Docker Compose deployment

1. View CONFIG FILES for the neutree-core project:

   docker compose ls

2. Set the Compose file path in CONFIG FILES as the COMPOSE_FILE environment variable:

   export COMPOSE_FILE=/absolute/path/neutree-deploy/neutree-core/docker-compose.yml

3. Update neutree-core and neutree-api:

   # If the control plane images are local images, you do not need to run the following pull command.
   docker compose -p neutree-core -f "$COMPOSE_FILE" pull \
     neutree-core neutree-api
   docker compose -p neutree-core -f "$COMPOSE_FILE" up -d \
     --no-deps --force-recreate \
     neutree-core neutree-api

   Note:

   Specify only the neutree-core and neutree-api services, and do not run down to avoid affecting other services.

4. Confirm that both services have returned to the running state:

   docker compose -p neutree-core -f "$COMPOSE_FILE" ps \
     neutree-core neutree-api