id: gismicroservice title: GIS Cloud Suite
GIS Cloud Suite On-demand Deployment Service Instructions
On-demand deployment package for installing GIS Cloud Suite begins to be provided since 11i(2023), you can enable/disable optional services according to actual conditions and configure third-party services. Please refer to Install GIS Cloud Suite for detailed configuration variables and parameter descriptions.
Functions affected by disabling the services in the values.yaml file are detailed in the table below:
Functionality Affected after Disabling the Service
| Functional Modules | Options | Corresponding Service Name | Whether the Corresponding Service is Required | Whether the Configuration of External Third-Party Services is Supported | Effect of Disabling the Service(also without Third-Party Services) |
|---|---|---|---|---|---|
| deploy_disable_ingress | nginx-ingress-controller | √ | GIS Cloud Suite Ingress controller, once disabled, will not be able to set the domain name | ||
| License Center | deploy_disable_bslicense | bslicense-server | √ | √ | License Center back-end |
| deploy_bslicense_ui_host/port | bslicense-ui | √ | License center client, affecting the view of license center interface.Notes: If the backend is disabled, the service cannot take effect even after configuration | ||
| deploy_disable_iserver_geometry | iserver-geometry | GIS Cloud Suite Geometry Service | |||
| deploy_disable_iserver_datacatalog | iserver-datacatalog | GIS Cloud Suite Data Catalog Service | |||
| deploy_disable_iserver_config | iserver-config | GIS Cloud Suite Configuration Center, used for unified management of various service configurations | |||
| deploy_disable_image_service_webui | image-service-webui | GIS Cloud Suite Image Service Retrieval Web Client | |||
| deploy_disable_iserver_streaming_modelconfiger | iserver-streaming-modelconfiger | GIS Cloud Suite Stream Processing Model Editor | |||
| deploy_disable_copy_oracle_client | copy-oracle-client | Used to copy Oracle clients, volumed for use by GIS services, interface backend APIs, and other services. Only required when publishing Oracle workspace data sources | |||
| deploy_disable_file_manager | file-manager | GIS Cloud Suite File Manager | |||
| deploy_disable_hadoop_yarn_file_manager | hadoop-yarn-file-manager | GIS Cloud Suite Hadoop YARN File Manager | |||
| deploy_disable_gp_file_manager | gp-file-manager | GIS Cloud Suite Geoprocessing File Manager | |||
| deploy_disable_consul_server | consul-server | √ | √ | Used to provide service discovery, service configuration, and service harvesting functions | |
| GIS Cloud Suite Database | deploy_disable_ispeco_database | ispeco-mysql | √ | √ | Database for storing interface backend API information in GIS cloud suite |
| deploy_disable_ispeco_phpmyadmin | ispeco-phpmyadmin | √ | GIS Cloud Suite ispeco-mySQL Web Client.Notes: If ispeco-mysql is disabled, this function will be affected even if third-party services are enabled or configured | ||
| GIS Cloud Suite User Center | deploy_disable_keycloak | keycloak | √ | √ | GIS Cloud Suite User Center, used for user management to ensure security and unity |
| deploy_disable_keycloak_postgresql | keycloak-postgresql | √ | √（Before configuration, a "keycloak" database needs to be created） | Used for storing Keycloak data.Notes: If keycloak is disabled, this function will be affected even if third-party services are enabled or configured | |
| deploy_disable_rabbitmq | rabbitmq | √ | √ | GIS Cloud Suite Message Notification Service | |
| deploy_disable_redis | redis | √ | √ | Redis service of GIS Cloud Suite, used to store temporary resources for GIS services, service lists, and database services stored in service gateway sessions | |
| GIS iPortal Module | deploy_disable_iportal | iportal | After disabling, the GIS iPortal module and related services such as iportal proxy, iportal datainsights, and iportal dataviz cannot be used | ||
| deploy_disable_iportal_database | iportal-mysql | √（Before configuration, it is necessary to create databases such as "ipoortal", "ispeco", and "monitor"） | iPortal database service in GIS Cloud Suite, used to store iPortal user informationNotes: If iportal is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_iportal_phpmyadmin | iportal-phpmyadmin | √ | iPortal-MySQL web client in GIS Cloud Suite.Notes: If iportal or iportal-mysql is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_iportal_postgis | iportal-postgis | √（Before configuration, a "structureddata" database needs to be created） | The PostGIS database service of iPortal in the GIS Cloud Suite, used to support the MapStudio WebApp.Notes: If iportal is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_iportal_memcached | iportal-memcached | √ | Built-in caching system for iPortal in GIS Cloud SuiteNotes: If iportal is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_iportal_elasticsearch | iportal-elasticsearch | √ | The Elasticsearch service of iPortal in GIS Cloud Suite, used for distributed retrieval of iPortal.Notes: If iportal is disabled, this function will be affected even if third-party services are enabled or configured | ||
| System Monitoring | deploy_disable_prometheus | prometheus | √（Should be deployed to the same namespace as the iManager machine） | The monitoring system service of GIS Cloud Suite, if disabled, will not be able to monitor the resource load | |
| deploy_disable_prometheus_node_exporter | prometheus-node-exporter | √ | Node Monitoring function of GIS Cloud Suite.Notes: If prometheus is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_kube_state_metrics | kube-state-metrics | √ | The metric library function of monitoring indicators in the GIS Cloud Suite, used to monitor container status.Notes: If prometheus is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_metrics_server | metrics-server | √ | Used for Kubernetes resource monitoring and dynamic scaling function.Notes: If prometheus is disabled, the resource indicators for monitoring K8s will be affected even if third-party services are enabled or configured | ||
| deploy_disable_blackbox_exporter | blackbox-exporter | √ | GIS Service Instance Status Monitoring and Detection Functions of GIS Cloud Suite | ||
| Analysis and Monitoring platform | deploy_disable_grafana | grafana | √ | Analysis and monitoring platform for GIS Cloud Suite, used to display monitoring load information | |
| deploy_disable_grafana_postgresql | grafana-database | √（The "grafana" database needs to be created first） | The PostgreSQL database service of Grafana, used to store Grafana data.Notes: If grafana is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_k8s_dashboard | k8s-dashboard | √ | The command line and container log viewing functions of GIS Cloud Suite. After disabling, "Log" and "Command Line" will not be available |
Notes：
When “deploy_disable_prometheus”、“deploy_disable_blackbox_exporter” are configured as third-party services, their usage will be temporarily restricted. Please configure them carefully.