Navigation API | On-Premise | 2GIS Documentation

Updating navigation API services

You can update navigation services together with its data or without it. To download data only, you need to update the Navi-Castle service only. In other cases, update all required navigation services.

  1. Fetch new installation artifacts.

    • To update only the service image, add the --only-apps flag after the pull command.
    • To update only data, add the --only-data flag after the pull command.
    • To update both service and data, run the command without flags above.

    To get artifacts for the navigation services only, add --services=navi after the pull command. Without this parameter artifacts for all services will be fetched by default. See the reference of DGCLI command-line arguments.

  2. Copy the path to a new manifest file from the command output and set it as a value to the dgctlStorage.manifest parameter in the values-castle.yaml configuration file. For more information, see the service installation instructions.

    Important

    You can configure the process of importing new data for Navi-Castle. Use the importer settings group of the configuration file. If during a regular update of the navigation services you do not want to import new data, specify the manifest used for the previous import. In other cases, using a new manifest is recommended.

  3. Check out breaking changes. If necessary, update other settings in the values-castle.yaml configuration file.

  4. Run the command to update the service:

    helm upgrade --version=1.25.0 --atomic --values ./values-castle.yaml navi-castle 2gis-on-premise/navi-castle
    
  5. Test if the update succeeded.

Do the following steps for each Navi-Back instance installed:

  1. Fetch new installation artifacts.

    To get artifacts for the navigation services only, add --services=navi after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of DGCLI command-line arguments.

  2. Check out breaking changes. If necessary, update settings in the values-back.yaml configuration file. For more information, see the service installation instructions.

  3. Run the command to update the service:

    helm upgrade --version=1.25.0 --atomic --values ./values-back.yaml navi-back 2gis-on-premise/navi-back
    
  4. Test if the update succeeded.

  1. Fetch new installation artifacts.

    To get artifacts for the navigation services only, add --services=navi after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of DGCLI command-line arguments.

  2. Check out breaking changes. If necessary, update settings in the values-router.yaml configuration file. For more information, see the service installation instructions.

  3. Run the command to update the service:

    helm upgrade --version=1.25.0 --atomic --values ./values-router.yaml navi-router 2gis-on-premise/navi-router
    
  4. Test if the update succeeded.

  1. Fetch new installation artifacts.

    To get artifacts for the navigation services only, add --services=navi after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of DGCLI command-line arguments.

  2. Check out breaking changes. If necessary, update settings in the values-front.yaml configuration file. For more information, see the service installation instructions.

  3. Run the command to update the service:

    helm upgrade --version=1.25.0 --atomic --values ./values-front.yaml navi-front 2gis-on-premise/navi-front
    
  4. Test if the update succeeded.

  1. Fetch new installation artifacts.

    To get artifacts for the navigation services only, add --services=navi after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of DGCLI command-line arguments.

  2. Check out breaking changes. If necessary, update settings in the values-navi-async-matrix.yaml configuration file. For more information, see the service installation instructions.

  3. Run the command to update the service:

    helm upgrade --version=1.25.0 --atomic --values ./values-navi-async-matrix.yaml navi-async-matrix 2gis-on-premise/navi-async-matrix
    
  4. Test if the update succeeded.

  1. (Recommended) Back up data used by the service.

  2. Fetch new installation artifacts.

    To get artifacts for the navigation services only, add --services=navi after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of DGCLI command-line arguments.

  3. Check out breaking changes. If necessary, update settings in the values-restrictions.yaml configuration file. For more information, see the service installation instructions.

  4. Run the command to update the service:

    helm upgrade --version=1.25.0 --atomic --values ./values-restrictions.yaml navi-restrictions 2gis-on-premise/navi-restrictions
    
  5. Test if the update succeeded.