SuperMap iManager K8S
简体中文

Guides

Install iManager

This guide is used for deploying iManager on Kubernetes. There are two ways when you installing iManager, they are using Linux command and Helm command, choose either one is good.

All the packages introduced below can be downloaded from the link:

https://pan.baidu.com/s/1lWLyyT1jAbADGuxEG3m4gA

Password: ge4d

Requirement

  1. The Kubernetes environment v1.17 or higher(If you want to use the longhorn-xxx-deploy package provided by Netdisk to deploy Longhorn, you need to ensure that the Kubernetes environment v1.18 or higher. If you want to use the kubernetes-serverless-xxx-deploy package provided by Netdisk to deploy a Serverless environment, you need to ensure that the Kubernetes environment v1.20 or higher). Please make sure the time of node machines are the same as master machine(The time difference should be less than 30 seconds)

    If you do not have Kubernetes environment, please refer to Deployment Guide > Install Kubernetes > CentOS(Ubuntu) to install.

  2. Resources requirement:

    • Number of processors: 4 Cores+
    • Memory: 16 GB+
    • Disk: 200 GB+(200 GB is the minimum reserved size, not including industry data)
    • The environments which are created by iManager need extra resources

  3. The supermap-imanager-for-kubernetes-11.1.1-linux-x64.tar.gz package

    Path: iManager部署包/iManager 11.1.1/iManager for Kubernetes部署包/supermap-imanager-for-kubernetes-11.1.1-linux-x64.tar.gz

  4. The NFS Server installation package(Download the version of the NFS Server package according to your system. If you already have NFS Server, skip this step)

    Path(CentOS): iManager部署包/软件工具包/NFS Server离线安装包/nfs-server-offline-centos-7.5.zip

    Path(Ubuntu): iManager部署包/软件工具包/NFS Server离线安装包/nfs-server-offline-ubuntu-18.04.zip

  5. Images preparation(If you use Alibaba Cloud registry, skip this step)

    Path：iManager部署包/iManager 11.1.1/iManager for Kubernetes部署包/supermap-imanager-for-kubernetes-registry-all-11.1.1-linux-x64.tar.gz

  6. If you choose Helm command to install iManager, you need to install helm package

Install NFS Server

The example below is installing on CentOS, it is almost the same as install on Ubuntu. If you have NFS Server, skip this step.

  • Unzip the nfs-server-offline-centos-7.5.zip package on the local machine

  • Copy the supermap-nfs-server folder to any of the Kubernetes machine

    Enter the supermap-nfs-server folder:

    cd supermap-nfs-server

    Execute:

    sudo chmod +x install.sh && ./install.sh

The path of the NFS storage directory is: /opt/nfs_data

The root user can execute the following commands to verify if the NFS has been installed:

mkdir test
mount -t nfs <ip>:/opt/nfs_data test

Notes:
<ip> is the machine IP where you installed the NFS on.

Non-root user can execute the following command:

service nfs status

The successful results are shown as below:

nfs-status-active

If storages such as NFS Server and Ceph are unavailable, you can install Longhorn Storage.

Install iManager Image Repository

If you install iManager on the extranet, skip this step and set Alibaba cloud registry.

Before installing the image registry, execute the command docker version to make sure you have installed Docker.

Notes:

It is better to use a new and clean machine to install the image registry.

  1. Put the image package in any directory and unzip(If the name of your package is not the same as below, replace the package name in the command to your package name):

    tar -zxf supermap-imanager-for-kubernetes-registry-all-11.1.1-linux-x64.tar.gz

  2. Enter the directory that you unzipped:

    cd supermap-imanager-for-kubernetes-registry-all-11.1.1-linux-x64

  3. Install image registry:

    chmod +x startup.sh && ./startup.sh

  4. Verify. Execute the following command, if no error prompts, you have successful installed image registry. Replace the IP below by the actual IP of your machine.

    docker pull IP:5000/supermap/scratch:latest-amd64

    If you install registry on ARM, change the image tag ‘latest-amd64’ to ‘latest-arm64’.

Install iManager

You need to open the port of “deploy_imanager_port”(the port is 31100 by default) in the values.yaml file, and open the port 6443, 9101, and 2049(open 2049 when using NFS for data storage). If you use Alibaba Cloud ECS Server, add the ports to safety group rules. What is more, please make sure the port 3307 and 9183 is available.

In the values.yaml file of the iManager on-demand deployment package, please refer to the iManager On-demand Deployment Service Instructions for the description of the functions affected by disabling these services.

Execute all the commands by administrator permission:

  1. Put the supermap-imanager-for-kubernetes-11.1.1-linux-x64.tar.gz package in any directory of Kubernetes master machine, and unzip(If the name of your package is not the same as below, replace the package name in the command to your package name):

    tar -zxf  supermap-imanager-for-kubernetes-11.1.1-linux-x64.tar.gz

  2. Enter the directory that you unzipped:

    cd supermap-imanager-for-kubernetes-11.1.1-linux-x64

  3. Execute the command to set iManager configurations:

    vi values.yaml

  4. Modify the parameters:

    Notes:

    1. The following configurations could only be set before starting, if you need any change, please execute ./startup.sh after modifying. The Helm command to update the configuration, please execute ‘helm upgrade imanager . -n supermap’.
    2. The configurations have default values, do not delete any configuration when modifying.
    3. The “Required” variables need to be modified by your actual environment. The “Optional” variables can keep in default, please do not delete the default values.
    4. The “required” parameters include the top 5 and these required parameters of deploy_disable_bslicense, deploy_disable_imanager_database, deploy_disable_imanager_gateway_redis, deploy_keycloak, deploy_disable_postgresql and their corresponding parameters (when these parameters have a value of True, which means that external services need to be configured, some corresponding parameters are also “required”).
    5. The content section of the default comments in the values.yaml file allows you to set the affinity and node tolerance of the specified node as appropriate. For detailed configuration rules, please refer to the official documentation of Kubernetes.
     # Required. The iManager image registry address. The default address is Alibaba cloud registry: registry.cn-beijing.aliyuncs.com. If you install iManager on the extranet, we recommended to keep in default.
 # If you install iManager on the intranet, please refer to Install iManager Image Registry above to install the registry, and fill the blank by the format <IP>:5000, <IP> is the machine IP on which you installed the registry, for example, 192.168.17.133:5000.
 deploy_registry: registry.cn-beijing.aliyuncs.com

 # Required. The external IP which is used for visiting Kubernetes. The IP cloud be any one of the Kubernetes node machines. For example, 192.168.17.110.
 deploy_kubernetes_public_ip:

 # Required. The administrator account name, used for logging iManager, the account name is admin by default. It is recommended to modify the account name before executing "./startup.sh".
 deploy_imanager_user_name: admin

 # Required(Optional if you have configured deploy_storage_class_name). Your NFS Server address, NFS Server is using for iManager data storage, the address could be IP or domain name, for example, 192.168.17.150. Please refer to Install NFS Server above to install NFS Server.
 # If you are going to use NFS Server for data storage, it is necessary to install NFS Client on the node machines of Kubernetes.
 deploy_nfs_server:

 # Required. The mount path of NFS Server, the default mount path is /. Fills in the actual mount path of your NFS Server. If you installed NFS Server by the package we provided, fills in the mount path as: /opt/nfs_data.
 deploy_nfs_path: /

 # Optional. The URL of Kubernetes master node, the value is https://kubernetes.default.svc by default, keep in default if your environment is private cloud.
 # It is required to configure if your environment is public cloud, execute the command 'kubectl cluster-info' to get the URL, for example, https://192.168.17.110:6443.
 deploy_kubernetes_master_url: https://kubernetes.default.svc

 # Optional. The Kubernetes node IP which is mapped by GIS Cloud Suite domain name(the IP that configured in DNS Server), required to configure if your GIS Cloud Suite has a domain name. The value is using the first Kubernetes node IP by default.
 deploy_domain_ip:

 # Optional. The name of your StorageClass, used for storing the data of iManager. StorageClass and NFS Server(deploy_nfs_server) are used for storing iManager data, if you configured both of them, the data will be stored in NFS Server.
 deploy_storage_class_name:

 # Optional. The Kubernetes namespace, the value is supermap by default, you can define a name by your requirement.
 # It is required to create a namespace by the command when using Helm Command to install iManager.
 deploy_namespace: supermap

 # Optional. The image pull policy, choose one of these:[Always|Never|IfNotPresent], the value is IfNotPresent by default.
 # Always: Pull the latest images from registry.
 # Never: Use local images and nerver pull the images from registry.
 # IfNotPresent: Use local images first. If local images are unavailable, pull the images from registry.
 deploy_image_pull_policy: IfNotPresent

 # Optional. The image pull secret, used for identity authentication when pulling private images. You need to create a resource with the same name as the Secret in the namespace of Kubernetes. Please refer Tutorial > Appendix > FAQ Question 6 to see see the concrete method.
 deploy_image_pull_secret: image-pull-secret

 # Optional. The name of namespace which stores images in registry, the default name is 'supermap', you can define the name by the requirement.
 deploy_image_namespace: supermap

 # Optional. The service type of iManager, fills in [NodePort|LoadBalancer], generally keep in default. 
 # If your environment is public cloud, the value here is: LoadBalancer.
 deploy_service_type: NodePort

 # Optional. The service protocol of iManager, fills in [http|https], the value is http by default.
 deploy_imanager_service_protocol: http

 # Optional. Disable the log function of iManager or not, fills in [true|false], the value is false by default.
 # true: Disable the log function of iManager.
 # false: Do not disable the log function of iManager.
 deploy_disable_log: false

 # Optional. Disable the alarm fuction of iManager or not, fills in [true|false], the default is false.
 # true: Disable the alarm function of iManager.
 # false: Do not disable the alarm function of iManager.
 deploy_disable_alert: false

 # Optional. The number of CPUs of a service in iManager, the number is 2 by default.
 deploy_cpu_limit: 2

 # Optional. The memory of a service in iManager, the memory should be larger than or equal to 4Gi, the memory is 4Gi by default.
 deploy_memory_limit: 4Gi

 # Optional. The image tag of iServer in iManager.
 deploy_iserver_tag: 11.1.1-amd64

 # Optional. The image tag of iPortal in iManager.
 deploy_iportal_tag: 11.1.1-amd64

 # Optional. The image tag of iDesktop in iManager.
 deploy_idesktop_tag: 11.1.1-amd64

 # Optional. The image tag of iserver_gisapplication in iManager.
 deploy_gis_app_tag: 11.1.1-amd64

 # Optional. The port of iManager, select the range between 30000-32767, except 31234, the default is 31100. If you define a port, make sure the port is different to others port setting.
 deploy_imanager_port: 31100

 # Optional. Whether the license center is going to disable local storage, fills in [true|false], the value is false by default. When the value is true, you must configure either deploy_nfs_server or default_storage_class_name.
 # true: License center do not use local storage.
 # false: License center use local storage.
 deploy_disable_bslicense_local_volume: false

 # Optional. HBase capability optimization, fills in [true|false]. If you would not use HBase environment, keep in default. If you want to optimize built-in HBase, set the value to true, and refer Question 9 in Tutorial > Appendix > FAQ to create PV.
 deploy_disable_hbase_nfs_volume: false

 # Optional. The WeChat Work application's Token, required to configure when using Wechat alarm. Please refer to SuperMap iManager Documentation(Tutorial > Alarm Service > WeChat Work Alarm > WeChat Work Alarm Creation) to configure the Wechat Work alarm.
 deploy_weixin_token:

 # Optional. The WeChat Work Company ID, required to configure when using Wechat alarm.
 deploy_weixin_corp_id:

 # Optional. The WeChat Work application's EncodingAESKey, required to configure when using Wechat alarm.
 deploy_weixin_encoding_aes_key:

 # Optional. The WeChat Work Department ID, required to configure when using Wechat alarm.
 deploy_weixin_to_party:

 # Optional. The WeChat Work application's AgentId, required to configure when using Wechat alarm.
 deploy_weixin_agent_id:

 # Optional. The WeChat Work application's Secret, required to configure when using Wechat alarm.
 deploy_weixin_api_secret:

 # Optional. The webhook of Dingtalk, required to configure when using Dingtalk alarm. Please refer to SuperMap iManager Documentation(Tutorial > Alarm Service > Ding Talk Alarm > Ding Talk Alarm Creation) to configure the Dingtalk alarm.
 deploy_dingtalk_webhook:

 # Optional. The secret of Dingtalkk, required to configure when using Dingtalk alarm.
 deploy_dingtalk_secret:

 # Optional. The time zone of the system. Fill in the relative path in the directory /usr/share/zoneinfo/, such as Asia/Shanghai and America/New_York.
 deploy_timezone: Asia/Shanghai

 # Optional. Disable metrics server or not, metrics server is used for monitoring the resources of Kubernetes, fills in [true|false]. The value is false by default.
 # If the configured registry is private and metrics server is enabled, you need to create a resource with the same name as the secret value in kube-system namespace of Kubernetes. Please refer Tutorial > Appendix > FAQ Question 6 to see the concrete method.
 # true: Disable the metrics server.
 # false: Do not disable metrics server.
 deploy_disable_metrics_server: false

 # Optional. Enable Service Mesh(Istio) or not, fills in [true|false], the value is true by default.
 # If you use the ARM package, the Service Mesh is unavailable and the variable does not exist.
 # If the configured registry is private and Service Mesh function is enabled, you need to create a resource with the same name as the secret value in istio-system namespace of Kubernetes. Please refer Tutorial > Appendix > FAQ Question 6 to see the concrete method.
 # true: Enable Service Mesh.
 # false: Disable Service Mesh.
 deploy_istio_enabled: true

 # Optional. Enable ingressageteway and egressgateway in Service Mesh(Istio) or not, fills in [true|false], the value is true by default. Takes effect only if deploy_istio_enabled is true.
 # If you use the ARM package, the Service Mesh is unavailable and the variable does not exist.
 # true: Enable ingressageteway and egressgateway.
 # false: Disable ingressageteway and egressgateway.
 deploy_istio_enable_ingress_egress: true

 # Optional. Enable kiali and tracing in Service Mesh(Istio) or not, fills in [true|false], the value is true by default. Takes effect only if deploy_istio_enabled is true.
 # If you use the ARM package, the Service Mesh is unavailable and the variable does not exist.
 # true: Enable kiali and tracing.
 # false: Disable kiali and tracing.
 deploy_istio_enable_kiali_tracing: true

 # Optional. Enable asynchronous function in Serverless environment or not, fills in [true|false], the value is blank by default. Enable to take effect only if the system is with a Dapr environment.
 # true: Enable asynchronous function.
 # false: Disable asynchronous function.
 # If you do not fill the value, the system will fill the value automatically.
 deploy_async_function_enabled:

 # Optional. Enable synchronous function in Serverless environment or not, fills in [true|false], the value is blank by default. Enable to take effect only if the system is with a Knative environment.
 # true: Enable synchronous function.
 # false: Disable synchronous function.
 # If you do not fill the value, the system will fill the value automatically.
 deploy_sync_function_enabled: 
 
 # Required. Whether to disable the iManager License Center service, value range: [true | false]. The default value is false;
 # true: Disable the license center;
 # false: Enable the license center;
 # If disabled, it is necessary to configure external existing license center services.
 deploy_disable_bslicense: false

 # The backend host name of the license center that needs to be configured, which is required when disabling the iManager license center.
 deploy_bslicense_server_host:

 # The backend port number of the license center that needs to be configured, which is required when disabling the iManager license center.
 deploy_bslicense_server_port:

 # Optional. The client host name of the license center to be configured.
 deploy_bslicense_ui_host:

 # Optional. The client port number of the license center to be configured.
 deploy_bslicense_ui_port:

 # Required. whether to disable the business database storing iManager related information, value range: [true | false]. The default value is false;
 # true: Disable the iManager business database;
 # false: Enable the iManager business database;
 # If disabled, existing external database services need to be configured.
 deploy_disable_imanager_database: false

 # Optional. Configuring the database type of the existing database service. The optional configurations are mariadb and postgreSQL, with mariadb as the default;
 # After completing the creation of the database environment in iManager, you can configure MySQL or PostgreSQL database services created by iManager.
 deploy_imanager_database_type: mariadb

 # The host name of the external database service that needs to be configured, which is required when disabling the iManager business database.
 deploy_imanager_database_host:

 # The port number of the external database service that needs to be configured, which is required when disabling the iManager business database.
 deploy_imanager_database_port:

 # The username of the external database account that needs to be configured, which is required when disabling the iManager business database.
 deploy_imanager_database_username:

 # The password of the external database account that needs to be configured, which is required when disabling the iManager business database.
 deploy_imanager_database_password:

 # Optional. Whether to disable the web client database management tool of iManager, value range: [true|false]. The default value is false;
 # true: Disable the web client of the iManager database;
 # false: Enable the web client of the iManager database.
 deploy_disable_imanager_phpmyadmin: false

 # Optional. The host name of the iManager database web client.
 deploy_imanager_phpmyadmin_host:

 # The port number of the iManager database web client.
 deploy_imanager_phpmyadmin_port:

 # Required. Used for the database service stored in the gateway session. Whether to disable Redis for the iManager gateway. Value range: [true | false]. The default value is false;
 # true: Disable Redis for iManager gateway;
 # false: Enable Redis for iManager gateway;
 # If disabled, external existing Redis services need to be configured.
 deploy_disable_imanager_gateway_redis: false

 # The host name of the external Redis service that needs to be configured, which is required when disabling Redis for the iManager gateway.
 deploy_imanager_gateway_redis_host:

 # The port number of the external Redis service that needs to be configured, which is required when disabling Redis for the iManager gateway.
 deploy_imanager_gateway_redis_port:

 # The username of the external Redis service that needs to be configured, which is required when disabling Redis for the iManager gateway.
 deploy_imanager_gateway_redis_username:

 # The password of the external Redis service that needs to be configured, which is required when disabling Redis for the iManager gateway.
 deploy_imanager_gateway_redis_password:

 # Required. Whether to disable the iManager user center. Used for iManager user management to achieve security uniformity. Value range: [true | false]. The default value is false;
 # true: Disable the iManager user center;
 # false: Enable the iManager user center;
 # If disabled, it is necessary to configure external existing Keycloak services.
 # If the external Keycloak service is configured and the license center bslicense uses the iManager built-in service, then the license center cannot be accessed normally. For more information on the solution, please refer to GIS Cloud Suite > Appendix >FAQ Question 17.
 # If an external Keycloak service is configured and an error such as "Internal Server Error" is reported when accessing iManager's Keycloak, please refer to Tutorial >Appendix >FAQ Question 18 for more details on the solution.  
 deploy_disable_keycloak: false

 # The host name of the external Keycloak service to be configured, required when disabling the iManager user center.
 deploy_keycloak_host:

 # The port number of the external Keycloak service to be configured, required when disabling the iManager user center.
 deploy_keycloak_port:

 # The admin username of the external Keycloak service to be configured, required when disabling the iManager user center.
 deploy_keycloak_admin_username:

 # The admin password of the external Keycloak service to be configured, required when disabling the iManager user center.
 deploy_keycloak_admin_password:

 # Required. Whether to disable the database service of Keycloak. Used to store data and information for Keycloak. Value range: [true | false]. The default value is false;
 # true: Disable the database for Keycloak;
 # false: Enable the database of Keycloak;
 # If disabled, existing external database services need to be configured to store Keycloak information.
 deploy_disable_keycloak_postgresql: false

 # The host name of the external keycloak database that needs to be configured, required when disabling the keycloak database.
 deploy_keycloak_postgresql_host:

 # The port number of the external keycloak database that needs to be configured, required when disabling the keycloak database.
 deploy_keycloak_postgresql_port:

 # The username of the external keycloak database that needs to be configured, required when disabling the keycloak database.
 deploy_keycloak_postgresql_username:

 # The password of the external keycloak database that needs to be configured, required when disabling the keycloak database.
 deploy_keycloak_postgresql_password:

 # Optional. Whether to disable the log harvesting function of iManager, value range: [true|false]. The default value is false;
 # true: Disable the iManager log harvesting function;
 # false: Enable the iManager log harvesting function.
 deploy_disable_fluentd_es: false

 # Optional. Whether to disable the Elasticsearch service of iManager. Used to store logs and access statistics records. Value range: [true | false]. The default value is false;
 # true: Disable iManager Elasticsearch;
 # false: Enable iManager Elasticsearch.
 deploy_disable_elasticsearch: false

 # Optional. The host name of the external Elasticsearch to be configured.
 deploy_elasticsearch_host:

 # Optional. The TCP protocol port number of the external Elasticsearch to be configured.
 deploy_elasticsearch_tcp_port:

 # Optional. The exposed ES RESTful interface port number of the external Elasticsearch to be configured for communication between the Elasticsearch node and the external.
 deploy_elasticsearch_rest_port:

 # Optional. Whether to disable the built-in services for displaying logs and access statistics in iManager. Used to visualize data in Elasticsearch. Value range: [true | false]. The default value is false;
 # true: Disable the display of logs and access statistics functions in iManager;
 # false: Enable the display of logs and access statistics functions in iManager;
 deploy_disable_kibana: false

 # Optional. The host name of the external Kibana to be configured.
 deploy_kibana_host:

 # Optional. The port number of the external Kibana to be configured.
 deploy_kibana_port:

 # Optional. The contextpath of the external Kibana to be configured.
 deploy_kibana_context_path:

 # Optional. Whether to disable the built-in database monitoring and automatic discovery services in iManager. Value range: [true|false]. The default value is false;
 # true: Disable database monitoring and service discovery functions in iManager;
 # false: Enable database monitoring and service discovery functions in iManager.
 deploy_disable_consul_server: false

 # Optional. The host name of the external Consul service to be configured.
 deploy_consul_server_host:

 # Optional. The port number of the external Consul service to be configured.
 deploy_consul_server_port:

 # Optional. Whether to disable the built-in monitoring system services of iManager. Used to monitor resource load. Value range: [true|false]. The default value is false;
 # true: Disable the monitoring system function in iManager;
 # false: Enable the monitoring system function in iManager.
 deploy_disable_prometheus: false

 # Optional. Whether to disable the alarm function in iManager, value range: [true|false]. The default value is false;
 # true: Disable the alarm function;
 # false: Enable the alarm function.
 deploy_disable_alert: false

 # Optional. Whether to disable the node monitoring function in iManager. Value range: [true|false]. The default value is false;
 # true: Disable the node monitoring function in iManager;
 # false: Enable the node monitoring function in iManager.
 deploy_disable_prometheus_node_exporter: false     

 # Optional.Whether to disable metrics_ Server service. Used for Kubernetes resource monitoring and can support dynamic scaling functionality. Value range: [true|false]. The default value is false;
 # If you have configured a private warehouse and enabled the metrics_ Server service, it is necessary to create a resource with the same name as Secret in the namespace of Kube system in Kubernetes. For details, please refer to Tutorial > Appendix > FAQ Question 17;
 # true: Disable the metrics_ Server service;
 # false: Enable the metrics_ Server service.
 deploy_disable_metrics_server: false
 
 # Optional. Whether to disable the  metric library function of monitoring indicators. Used to monitor container status. Value range: [true|false]. The default value is false;
 # true: Disable the Kubernetes status information monitoring function;
 # false: Enable the Kubernetes status information monitoring function.
 deploy_disable_kube_state_metrics: false
  
 # Optional. Whether to disable the URL monitoring function in iManager. Value range: [true|false]. The default value is false;
 # true: Disable the URL monitoring function;
 # false: Enable the URL monitoring function.
 deploy_disable_blackbox_exporter: false

 # Optional. Whether to disable the Kubernetes certificate expiration monitoring function in iManager. Value range: [true|false]. The default value is false;
 # true: Disable the Kubernetes certificate expiration monitoring function; If disabling and configuring external existed ssl_exporter service, you should deploy the ssl_exporter service in a certain namespace of the machine where the iManager is located, otherwise the monitored Kubernetes certificate will not belong to the iManager environment, but to the machine where the ssl_exporter service is located;
 # false: Enable the Kubernetes certificate expiration monitoring function.
 deploy_disable_ssl_exporter: false

 # Optional, the host name of the external ssl_exporter service to be configured.
 deploy_ssl_exporter_host:

 # Optional, the port number of the external ssl_exporter service to be configured.
 deploy_ssl_exporter_port:

 # Optional, whether to disable the built-in analysis and monitoring platform in iManager.Used to display monitoring load information. Value range: [true|false]. The default value is false;
 # If the built-in analysis and monitoring platform is disabled and configured as an external Grafana service, when the overview page load map cannot be displayed normally in traceless mode, it is necessary to allow the browser to use third-party cookies, that is, turn off the "Block third-party cookies" button;
 # true: Disable the dashboard used by iManager to display monitoring load information;
 # false: Enable the dashboard used by iManager to display monitoring load information;
 deploy_disable_grafana: false

 # Optional. The host name of the external Grafana to be configured.
 deploy_grafana_host:

 # Optional. The port number of the external Grafana to be configured.
 deploy_grafana_port:

 # Optional. The contexpath of the external Grafana to be configured.
 deploy_grafana_contetxt_path:

 # Optional. Whether to disable the PostgreSQL database service of Grafana. Used to store Grafana data. Value range: [true|false]. The default value is false;
 # true: Disable the Grafana database; To disable and configure external PostgreSQL database services, you need to first create a 'Grafana' database in PostgreSQL.
 # false: Enable the Grafana database.
 deploy_disable_grafana_postgresql: false

 # Optional. The host name of the external database to be configured for storing Grafana information.
 deploy_grafana_postgresql_host:

 # Optional. The port number of the external database to be configured for storing Grafana information.
 deploy_grafana_postgresql_port:

 # Optional. The username of the external database to be configured for storing Grafana information.
 deploy_grafana_postgresql_username:

 # Optional. The passport of the external database to be configured for storing Grafana information.
 deploy_grafana_postgresql_password:

 # Optional. Whether to disable the iManager command line and container log viewing function. Value range: [true|false]. The default value is false;
 # true: Disable the command line and container log viewing function;
 # false: Enable the command line and container log viewing function.
 deploy_disable_k8s_dashboard: false

 # Optional. The host name of the external service to be configured for providing command line and container log viewing function.
 deploy_k8s_dashboard_host:

 # Optional. The port number of the external service to be configured for providing command line and container log viewing function.
 deploy_k8s_dashboard_port:

 #affinity:
 # nodeAffinity:
 #    requiredDuringSchedulingIgnoredDuringExecution:
 #      nodeSelectorTerms:
 #        - matchExpressions:
 #            - key: kubernetes.io/hostname
 #              operator: Exists
 #tolerations:
 #  - key: "key1"  #Tolerable stains key
 #    operator: "Equal"  #Equal represents key=value; Exists indicates that the value will be ignored
 #    value: "value1"  #Value
 #    effect: "NoExecute"  #Strategy
 #    tolerationSeconds: 3600  #Used to describe the time during which a Pod can continue to run when it needs to be expelled. Note that only effect: "NoExecute" can be set, otherwise an error will be reported

    Notes:

    1. The password used by default is Supermap1997, please modify it in time.
    2. Using the same password for long is the main reason for password cracking. In an environment with extremely high security requirements, the default administrator password should be modified and updated regularly.
    3. If the password is too simple, it may be decrypted and brute-forced by malicious users who will steal important information and resources, posing security risks. Please try to update your password as complex as possible.
  5. Save and quit the file.

  6. Install iManager(Executing the following command in supermap-imanager-for-kubernetes directory):

    There are two ways to install iManager, Linux command and Helm command, choose either of them.

    Using Linux Command(When logs including “Kubernetes cluster unreachable”, see the iManager for K8s online help documentation Tutorial > Appendix > FAQ > Question 12)

    chmod +x startup.sh && ./startup.sh

    Using Helm Command

    6.1 Create a namespace which is named ‘supermap’(you can define the name of namespace, do not forget to change ‘supermap’ in next two steps to your defined name)

    kubectl create ns supermap

    6.2 Install iManager

    chmod +x ./helm
./helm install imanager . -n supermap

    6.3 Check if iManager is installed successfully

    ./helm list -n supermap

helmlist

Visit iManager UI by the address http://<ip>:31100 .Replace <ip> by the Master node IP of Kubernetes. If the value of deploy_imanager_service_protocol is https, the access address should be https://<ip>:31100.

The login account please refer to the administrator account information in values.yaml

Activate License

Click on Update on the License Center page, and follow the Operation Steps to activate the license (If you do not have the license, please apply the trial license on SuperMap official website).

activatelic

Check the License Status after activating the license.

licensestatus1

Appendix

1.Delete iManager

If you want to delete iManager environment, execute:

chmod +x shutdown.sh && ./shutdown.sh

If you want to completely delete iManager environment, execute:

chmod +x shutdown.sh && ./shutdown.sh -v

Using Helm command to delete iManager(the namespace and related environments will not be deleted):

./helm uninstall imanager -n supermap