Guides

Install GIS Cloud Suite - Kubernetes

TThis guide is used for quickly deploying GIS Cloud Suite on Kubernetes. There are two ways when you installing GIS Cloud Suite, 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

The Kubernetes environment v1.17 and 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). If you have multiple Kubernetes node machines, 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 or Ubuntu to install the environment.
The supermap-imanager-for-kubernetes-11.2.1-linux-x64-giscloudsuite.tar.gz package.
System Requirements:
- Number of processors: 4 cores+
- Memory: 16 GB+
- Disk: 200 GB+(200 GB is the minimum reserved size, not including industry data)
- The built-in environments need extra resources
GIS Cloud Suite package can be used for both single machine and multiple machines deploy. You need to configure NFS Server if you deploy on multiple machines.
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)
- nfs-server-offline-centos-7.5.zip
- nfs-server-offline-ubuntu-18.04.zip
Images registry(If you use Alibaba Cloud registry, skip this step. For specific methods, please refer to the “Combined Image Instructions” in the “Combined Image Packages” directory of the link)
- supermap-imanager-for-kubernetes-11.2.1-linux-x64-registry-all.tar.gz
- supermap-imanager-for-kubernetes-11.2.1-linux-x64-images-bigdata.tar.gz
- supermap-imanager-for-kubernetes-11.2.1-linux-x64-images-machinelearning.tar.gz
If you choose Helm command to install GIS Cloud Suite, you need to install helm package

Install NFS Server

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

Unzip nfs-server-offline-centos-7.5.zip package on the local machine
Copy supermap-nfs-server folder to any of the Kubernetes machine

Enter 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 successfully:

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:

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

Install GIS Cloud Suite Image Registry

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.

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-11.2.1-linux-x64-registry-all.tar.gz
```

Enter the directory that you unzipped:

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

Install image registry:
```
chmod +x startup.sh  && ./startup.sh
```
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 GIS Cloud Suite

The computer needs to open the ports corresponding to “httpport” (the default value is 32222), “httpsport” (the default value is 32223) in the values.yaml file, as well as ports 6443, 8443, 2049 (open when using NFS storage), 8080, and 9101. If you are using Alibaba Cloud ECS servers, you need to add the above ports to the security group rules. In addition, you also need to ensure that ports 3307 and 9183 are not occupied.

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

Execute all the following commands by root permission:

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.2.1-linux-x64-giscloudsuite.tar.gz
```

Enter the supermap-imanager-for-kubernetes-11.2.1-linux-x64-giscloudsuite directory, and execute:

vi values.yaml

Modify the values.yaml file:

Notes:

The following configurations could only be set before starting, if you need any change, please execute ./startup.sh after modifying.

The configurations have default values, do not delete any configuration when modifying.

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.

The “required” parameters include the top 3 parameters.

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 GIS Cloud Suite image registry address, used for pulling images. The address is Alibaba cloud registry by default: registry.cn-beijing.aliyuncs.com. If you install GIS Cloud Suite on the extranet, keep in default.
  # If you install GIS Cloud Suite on the intranet, please refer to Install GIS Cloud Suite Image Registry above to install the registry, and fill the blank by the format <IP>:5000. Replace <IP> by the machine IP which you were installed registry on, for example, 192.168.17.110:5000.
  registry: registry.cn-beijing.aliyuncs.com

  # Required. The external IP of Kubernetes, used for visiting Kubernetes UI. The IP could be any one of the Kubernetes node machines' IP. For example, 192.168.17.110.
  kubernetes_public_ip:

  # Required. The administrator account name, used for logging GIS Cloud Suite, the account name is admin by default. It is recommended to modify the account name before executing "./startup.sh".
  username: supermap

  # Optional(Required if you install iManager on multiple machines without configuring 'deploy_storage_class_name'). Your NFS Server address, NFS Server is used for storing the data of GIS Cloud Suite, recommended to set, the address could be IP or domain name. For example: 192.168.17.150. Please refer 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.
  nfs_server:

  # Optional. The path of NFS server, the default path is /. If you install NFS by the NFS package provided by SuperMap, the path below should be: /opt/nfs_data. If you do not configure NFS Server, the default data volume is hostPath, located on /opt/giscloudsuite directory.
  nfs_path: /

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

  # 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.
  kubernetes_master_url: https://kubernetes.default.svc


  # Optional. The Kubernetes namespace, the value is giscloudsuite 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 GIS Cloud Suite.
  deploy_namespace: giscloudsuite

  # Optional. The service protocol of GIS Cloud Suite，fills in [http|https], the value is http by default.
  deploy_service_protocol: http

  # Optional. The port of GIS Cloud Suite UI, select the range between 30000-32767, except 31234, the default is 32222. If you define a port, make sure the port is different to others port setting.
  http_port: 32222

  # Optional, the UI access entry port for GIS Cloud Suite to open the HTTPS protocol, custom range: 30000-32767, excluding 31234, default 32223. If you customize the port, be careful not to use the same port as other configuration items.
  https_port: 32223  

  # 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 GIS Cloud Suite > Appendix > FAQ Question 12 to see how to create the resource.
  deploy_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.
  image_namespace: supermap

  # Optional. The image tag of iserver_gisapplication in GIS Cloud Suite.
  image_tag: 11.2.1-amd64

  # Optional. The number of CPUs of a service in GIS Cloud Suite, the number is 2 by default.
  cpu_limit: 2

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

  # Optional. Whether to enable iPortal, fills in [true|false], the value is true by default.
  # true: Enable iPortal.
  # false: Disable iPortal
  iportal_enabled: true

  # Optional, whether to enable the GIS cloud suite remote sensing image data processing and production function, value range: [true|false]. Default is false;
  # true: Enable remote sensing image processing function;
  # false: Do not enable remote sensing image processing function.     
  imagex_enabled: false

  # 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.
  bslicense_local_volume_enabled: true

  # Optional, whether to enable the built-in Ingress controller of the GIS cloud suite. If disabled, the domain name cannot be set. The value range is [true|false]. The default value is false;
  # true: Enable the Ingress controller;
  # false: Disable the Ingress controller.
  builtin_ingress_enabled: false
   
  # 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.
  domain_ip:

  # Optional, Ingress service type, value range: [ClusterIP|LoadBalancer], usually keep the default;
  # If it is a public cloud environment such as Alibaba Cloud, fill in LoadBalancer here.
  ingress_service_type: ClusterIP

  # Optional. The domain name of GIS Cloud Suite, for example, imanager.iservergateway.com. Visit GIS Cloud Suite by ip:port if you do not configure domain name.
  gateway_domain:

  # Optional. The directory which to store the certificate of GIS Cloud Suite domain name. Take effect only if configured GIS Cloud Suite domain name(deploy_gateway_domain). The directory of certificate should be the same as values.yaml file. Fill in the relative path. such as: gateway/tls.crt.
  gateway_certificate_path:

  # Optional. The directory which to store the private key of GIS Cloud Suite domain name. Take effect only if configured GIS Cloud Suite domain name(deploy_gateway_domain). The directory of private key should be the same as values.yaml file. Fill in the relative path, such as: gateway/tls.key.
  gateway_private_key_path:

  # 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.
  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 true by default.
  # true: Disable the metrics server.
  # false: Do not disable metrics server.
  builtin_imanager_metrics_server_enabled: 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.
  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.
  sync_function_enabled:
  
  # Cluster permission range, value range: [cluster|namespace|custom]. Cluster (cluster) has all permissions, namespace (namespace) can only be operated and used in the namespace configured in the "namespace" item, and custom (custom) is the permission of the service account (ServiceAccount) you provide yourself;
  # When configuring to custom, you need to configure "service_account_name" at the same time, that is, the ServiceAccount you create yourself. For other precautions, please refer to the iManager for K8s online help document, Guides -> Deployment Guide-> Install iManager -> Install the Deployment Center -> Appendix 1.
  service_account_scope: CLUSTER

  # Required. Whether to disable the GIS Cloud Suite License Center service, value range: [true|false]. The default value is true;
  # true: Enable the license center;
  # false: Disable the license center;
  # If disabled, it is necessary to configure external existing license center services.
  builtin_bslicense_enabled: true

  # The backend host name of the license center that needs to be configured, which is required when disabling the GIS Cloud Suite license center.
  bslicense_server_host:

  # The backend port number of the license center that needs to be configured, which is required when disabling the GIS Cloud Suite license center.
  bslicense_server_port:

  # The client host name of the license center to be configured，which is required when disabling the GIS Cloud Suite license center.
  bslicense_ui_host:

  # License center port. Be careful not to use the same port as other configuration items. Required when disabling the GIS Cloud Suite License Center
  bslicense_ui_port: 

  # Optional. Whether to enable the GIS Cloud Suite geometry service, value range: [true|false]. The default value is ture;
  # true: Enable the geometry service;
  # false: Disable the geometry service.
  iserver_geometry_enabled: true

  # Optional. Whether to enable the GIS Cloud Suite data catalog service, value range: [true|false]. The default value is true;
  # true: Enable the data catalog service;
  # false: Disable the data catalog service.
  iserver_datacatalog_enabled: true

  # Optional, whether to enable the built-in file manager of GIS Cloud Suite, value range: [true|false]. Default is true;
  # true: Enable the file manager;
  # false: Disable the file manager.
  cloudsuite_file_manager_enabled: true
  
  # Optional, whether to enable the built-in hadoop yarn file manager of the GIS cloud suite, value range: [true|false]. Default is true;
  # true: Enable Hadoop YARN file manager;
  # false: Disable Hadoop YARN file manager.  
  cloudsuite_hadoop_yarn_file_manager_enabled: true

 # Optional, whether to enable the built-in geoprocessing file manager of GIS Cloud Suite, value range: [true|false]. Default is true;
 # true: Enable geoprocessing file manager;
 # false: Disable geoprocessing file manager.
  cloudsuite_gp_file_manager_enabled: true

  # Optional. Whether to enable the built-in stream processing model editor in GIS Cloud Suite, value range: [true|false]. The default value is trie;
  # true: Disable the stream processing model editor;
  # false: Enable the stream processing model editor.
  iserver_streaming_modelconfiger_enabled: true

  # Optional. Whether to disable the image search web client in GIS Cloud Suite, value range: [true|false]. The default value is true;
  # true: Disable the image search web client;
  # false: Enable the image search web client.
  iserver_image_service_webui_enabled: true

  # Optional. Whether to enable the built-in services for copying and mounting Oracle clients in the GIS Cloud Suite, which are used by GIS services, interface backend APIs, and other services. Oracle workspaces need to be published for use, value range: [true|false]. The default value is true; 
  # true: Enable the built-in services for copying and mounting Oracle clients;
  # false: Disable the built-in services for copying and mounting Oracle clients.
  cloudsuite_copy_oracle_client_enabled: true

  # Required. Whether to enable the database for storaging interface backend API information in the GIS Cloud Suite, value range: [true|false]. The default value is true;
  # true: Enable the GIS Cloud Suite database service; If using external services, it is necessary to first complete the creation of the "iSpeco" database;
  # false: Disable the GIS Cloud Suite database service;
  builtin_cloudsuite_database_enabled: true

  # Optional. Configure the database type of the existing database service, which can be configured as mariadb and postgresql, with postgresql as the default.
  cloudsuite_database_type: postgresql

  # The host name of the external database service that needs to be configured, which is required when disabling the GIS Cloud Suite database.
  cloudsuite_database_host:

  # The port number of the external database service that needs to be configured, which is required when disabling the GIS Cloud Suite database.
  cloudsuite_database_port:

  # The username of the external database service that needs to be configured, which is required when disabling the GIS Cloud Suite database.
  cloudsuite_database_username:

  # The passport of the external database service that needs to be configured, which is required when disabling the GIS Cloud Suite database.
  cloudsuite_database_password:

  # Optional. Whether to enable the database client in the GIS Cloud Suite, value range: [true|false]. The default value is false;
  # true: Enable the GIS Cloud Suite database client;
  # false: Disable the GIS Cloud Suite database client.
  builtin_cloudsuite_database_client_enabled: false

  # Required. Whether to enable the Consul service in the GIS Cloud Suite. Used for service discovery, service configuration, and service harvesting. Value range: [true | false]. The default value is true;
  # true: Enable the Consul service in the GIS Cloud Suite;
  # false: Disable the Consul service in the GIS Cloud Suite.
  builtin_cloudsuite_consul_enabled: true

  # The host name of the external Consul service to be configured, required when disabling Consul service in the GIS Cloud Suite.
  cloudsuite_consul_host:

  # The port number of the external Consul service to be configured, required when disabling Consul service in the GIS Cloud Suite.
  cloudsuite_consul_port:

  # Required. Whether to enable the built-in user center of the GIS Cloud Suite. Used for user management to achieve security uniformity. Value range: [true|false]. The default value is true;
  # true: Enable the GIS Cloud Suite user center;
  # false: Disable the GIS Cloud Suite user center;
  # If disabled, it is necessary to configure external existing Keycloak services.
  builtin_cloudsuite_keycloak_enabled: true

  # The host name of the external Keycloak service that needs to be configured, which is required when disabling the built-in user center of the GIS Cloud Suite,
  cloudsuite_keycloak_host:

  # Required when disabling the built-in user center of the GIS Cloud Suite, custom range: 30000-32767, excluding 31234. When customizing ports, be careful not to use the same ports as other configuration items.
  cloudsuite_keycloak_port:

  # The admin username of the external Keycloak service that needs to be configured, required when disabling the built-in user center of the GIS Cloud Suite.
  cloudsuite_keycloak_username:

  # The admin password of the external Keycloak service that needs to be configured, required when disabling the built-in user center of the GIS Cloud Suite.
  cloudsuite_keycloak_password:

  # Required. Whether to enable the database service of Keycloak in GIS Cloud Suite. Used to store data and information for Keycloak. Value range: [true|false]. The default value is true;
  # true: Enable the database for Keycloak; to disable the built-in Keycloak database and configure external services, it is necessary to first complete the creation of the "keycloak" database;
  # false: Disable the database of Keycloak;
  # If disabled, existing external database services need to be configured to store Keycloak information.
  builtin_cloudsuite_keycloak_database_enabled: true

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

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

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

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

  # Required. Whether to enble the built-in message notification service of the GIS Cloud Suite. Value range: [true|false]. The default value is true;
  # true: Enable the message notification service;
  # false: Disable the message notification service;
  # If disabled, it is necessary to configure external RabbitMQ services for message notifications.
  builtin_cloudsuite_rabbitmq_enabled: true

  # The host name of the external RabbitMQ service that needs to be configured, required when disabling the message notification service.
  cloudsuite_rabbitmq_host: 

  # The port number of the external RabbitMQ service that needs to be configured, required when disabling the message notification service.
  cloudsuite_rabbitmq_port:

  # The username of the external RabbitMQ service that needs to be configured, required when disabling the message notification service.
  cloudsuite_rabbitmq_username:

  # The password of the external RabbitMQ service that needs to be configured, required when disabling the message notification service.
  cloudsuite_rabbitmq_password:

  # Required. Whether to enable Redis service for the GIS Cloud Suite, Used for storing temporary resources for GIS services, service lists, and database services storing in service gateway sessions. Value range: [true|false]. The default value is true;
  # true: Enable Redis for the GIS Cloud Suite;
  # false: Disable Redis for the GIS Cloud Suite;
  # If disabled, external existing Redis services need to be configured.
  builtin_cloudsuite_redis_enabled: true

  # The host name of the external Redis service that needs to be configured, which is required when disabling Redis for GIS Cloud Suite.
  cloudsuite_redis_host: 

  # The port number of the external Redis service that needs to be configured, which is required when disabling Redis for GIS Cloud Suite.
  cloudsuite_redis_port:

  # The username of the external Redis service that needs to be configured, which is required when disabling Redis for GIS Cloud Suite.
  cloudsuite_redis_username:

  # The password of the external Redis service that needs to be configured, which is required when disabling Redis for GIS Cloud Suite.
  cloudsuite_redis_password:

  # Optional. Whether to enable the iPortal database service of the GIS Cloud Suite. Used to store iPortal user information. Value range: [true|false]. The default value is true;
  # true: Enable Redis of the GIS Cloud Suite;
  # false: Disable Redis of the GIS Cloud Suite.
  builtin_iportal_database_enabled: true

  # Optional. Configure the database type of the existing database service, which can be configured as mysql and postgresql, and default to postgresql; 【To switch to a postgresql database, you need to first start iPortal and go to the iPortal mount path before switching to the database, then modify the iportal-monitor.xml file in the WEB-INF path. For details, Please refer to GIS Cloud Suite >Appendix >FAQ Question 26】
  # When configuring external MySQL, it is necessary to first create the "iPortal", "iSpeco", and "monitor" databases.
  iportal_database_type: 

  # Optional. The host name of the external database service to be configured.
  iportal_database_host:

  # Optional. The port number of the external database service to be configured.
  iportal_database_port:

  # Optional. The username of the external database service to be configured.
  iportal_database_username: 

  # Optional. The passport of the external database service to be configured.
  iportal_database_password:

  # Optional. Whether to enable the built-in iPortal PostGIS database service in the GIS Cloud Suite. Used to support MapStudio, value range: [true|false]. The default value is false;
  # true: Enable the built-in PostGIS database of iPortal. To disable and configure external services, you need to first complete the creation of the 'structuraldata' database;
  # false: Disable the built-in PostGIS database of iPortal.
  builtin_iportal_postgis_enabled: true

  # Optional. The host name of the external database service to be configured.
  iportal_postgis_host:

  # Optional. The port number of the external database service to be configured.
  iportal_postgis_port:
   
  # Optional. The username of the external database service to be configured.
  iportal_postgis_username:

  # Optional. The password of the external database service to be configured.
  iportal_postgis_password:

  # Optional. Whether to enable the built-in caching system of iPortal in the GIS Cloud Suite, value range: [true|false]. The default value is false;
  # true: Enable the built-in caching system of iPortal;
  # false: Disable the built-in caching system of iPortal.
  builtin_iportal_memcached_enabled: true
  
  # Optional. The host name of the external caching system to be configured.
  iportal_memcached_host:

  # Optional. The port number of the external caching system to be configured.
  iportal_memcached_port:

  # Optional. Whether to enable the built-in Elasticsearch service of iPortal in the GIS Cloud Suite, which can be used for distributed retrieval of iPortal. Value range: [true|false]. The default value is true;
  # true: Enable the built-in Elasticsearch of iPortal;
  # false: Disable the built-in Elasticsearch of iPortal.
  builtin_iportal_elasticsearch_enabled: true

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

  # Optional. The exposed ES RESTful interface port number of the external Elasticsearch to be configured, used for Elasticsearch nodes and external communication.
  iportal_elasticsearch_rest_port:

  # Optional. Whether to enable the built-in monitoring system service in the GIS Cloud Suite. Used to monitor resource load. Value range: [true|false]. The default value is true;
  # true: enable the built-in monitoring system function of the GIS Cloud Suite;
  # false: Disable the built-in monitoring system function of the GIS Cloud Suite.
  builtin_imanager_prometheus_enabled: true

  # Optional. Whether to disable the built-in measurement library function for monitoring indicators. Value range: [true|false]. The default value is true;
  # true: Enable the built-in measurement library function for monitoring indicators;
  # false: Disable the built-in measurement library function for monitoring indicators.   
   builtin_imanager_kube_state_metrics_enabled: true

  # Optional. Whether to disable the container metric collector in the GIS Cloud Suite. Value range: [true|false]. The default value is true;
  # true: Disable the container metric collector;
  # false: Enable the container metric collector.
  builtin_imanager_cadvisor_enabled: true

  # Optional. Whether to disable the built-in GIS service instance status monitoring and detection function of the GIS Cloud Suite, value range: [true|false]. The default value is false;
  # true: Disable the GIS service instance status detection function;
  # false: Enable the GIS service instance status detection function.
  builtin_imanager_blackbox_exporter_enabled: true

  # Optional. The host name of the external blackbox_exporter service to be configured.
  imanager_blackbox_exporter_host:
  
  # Optional. The port number of the external blackbox_exporter service to be configured.
  imanager_blackbox_exporter_port:

  # Optional. Whether to enable the built-in analysis and monitoring platform of GIS Cloud Suite for displaying monitoring load information. Value range: [true|false]. Default true;
  # true: Enable the built-in monitoring load information service in the GIS Cloud Suite;
  # false: Disable the built-in monitoring load information service in the GIS Cloud Suite.
  builtin_imanager_grafana_enabled: true

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

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

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

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

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

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

  # Optional. The password of the external database to be configured for storing Grafana information.
  imanager_grafana_database_password:
  
  # Optional. Whether to enable the command line and container log viewing function in the GIS Cloud Suite. Value range: [true|false]. The default value is true;
  # true: Enable the command line and container log viewing function;
  # false: Disable the command line and container log viewing function.
  builtin_imanager_k8s_dashboard_enabled: true

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

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

  # Optional, whether to enable the iManager alarm function, value range: [true|false]. Default is true;
  # true: Enable the alarm function;
  # false: Disable the alarm function.
  builtin_imanager_alert_manager_enabled: true
  # Optional, whether to enable the built-in log harvesting function, value range: [true|false]. Default is true;
  # true: Enable the log harvesting function;
   # false: Disable the log harvesting function.
   builtin_imanager_fluentd_es_enabled: true

  # Optional, whether to enable the built-in Elasticsearch service for storing logs and access statistics. Value range: [true|false]. Default is true;
  # true: Enable Elasticsearch;
  # false: Disable Elasticsearch.
  builtin_imanager_elasticsearch_enabled: true

  # Optional. The external Elasticsearch host name to be configured.
  imanager_elasticsearch_host: 

  # Optional. The TCP protocol port number of the external Elasticsearch to be configured. It is used for communication between Elasticsearch clusters.
  imanager_elasticserarch_tcp_port: 

  # Optional. The http protocol port number of the external Elasticsearch to be configured, used for communication between the Elasticsearch node and the external environment.
  imanager_elasticsearch_http_port: 

  # Optional, whether to enable the built-in display log and access statistics service for visualizing data in Elasticsearch. Value range: [true|false]. Default is true;
  # true: Enable the display log and access statistics function;
  # false: Disable the display log and access statistics function.
  builtin_imanager_kibana_enabled: true

  # Optional. The external Kibana host name to be configured.
  imanager_kibana_host: 

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

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

  # affinity:
  #   nodeAffinity:
  #      requiredDuringSchedulingIgnoredDuringExecution:
  #        nodeSelectorTerms:
  #          - matchExpressions:
  #            - key: kubernetes.io/hostname
  #             operator: Exists
  # tolerations:
  #  - key: "key1"  #Tolerable tainted key
  #    operator: "Equal"  #Equal means key=value; Exists means value will be ignored
  #    value: "value1"  #Value
  #    effect: "NoExecute"  #Rule
  #    tolerationSeconds: 3600  #Used to describe the time that a Pod can continue to run when it needs to be evicted. Note that this can only be set if effect: "NoExecute" is set, otherwise an error will be reported.

Notes:

The password used by default is Supermap@1997, please modify it in time.

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.

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.

Save and quit the file.

Install:

There are two ways to install GIS Cloud Suite, they are using 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 GIS Cloud Suite > Appendix > FAQ > Question 22)
```
chmod +x startup.sh && ./startup.sh
```
Using Helm Command
1. Create a namespace which is named ‘giscloudsuite’(you can define the name of namespace, do not forget to change ‘giscloudsuite’ in the next two steps to your defined name)
```
kubectl create ns giscloudsuite
```
2. Install GIS Cloud Suite
```
chmod +x ./helm
./helm install giscloudsuite . -n giscloudsuite
```
3. Check if GIS Cloud Suite is installed successfully
```
./helm list -n giscloudsuite
```
After the installation is complete, you can access the GIS Cloud Suite page through http://<ip>:32222. <ip>: is the ip of the kubernetes Master node. When the value of protocol is https, it can be accessed through https://<ip>:32223; when the value of protocol is http_https, it can be accessed through http://<ip>:32222 and https://<ip>:32223.

{ip}: the IP of kubernetes Master machine.

Refer to the settings of values.yaml file to see the username and password.
Activate License

Visit the SuperMap License Center UI, 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).

Check the License Status after activating the license.

Appendix

The access addresses of the basic services({ip}: is the IP of Kubernetes Master machine):

Service Address

GIS Cloud Suite http://{ip}:32222 or https://{ip}:32223