Tutorial
iManager On-demand Deployment Service Instructions
On-demand deployment package for installing iManager 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 iManager 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 | √ | iManager Ingress controller, if disabled will not set the domain. Ingress is not supported in K8s versions lower than 1.19，in where should be disabled | ||
| Alarm Service | deploy_disable_weixin_hook | imanager-weixin-hook | iManager WeChat Work Alarm and Remote Control functions. If disabled, WeChat Work Alarm cannot be configured | ||
| deploy_disable_web_hook | imanager-web-hook | iManager Ding Talk Alarm function. If disabled, Ding Talk Alarm cannot be configured | |||
| deploy_disable_alert | alertmanager | √ | iManager UI Alarm funciton. If disabled, UI UI Alarm funciton cannot be use | ||
| License Center | deploy_disable_bslicense | bslicense-server | √ | √ | License center back-end, disabling will affect the license connection |
| deploy_bslicense_ui_host/port | bslicense-ui | √ | License center client, affecting the view of license center interface.Notes:If the back-end is disabled, the service configuration will not work either | ||
| iManager Database | deploy_disable_imanager_database | imanager-mysql | √ | √ | iManager business database, disabling will not be able to store iManager information |
| deploy_disable_imanager_phpmyadmin | imanager-phpmyadmin | √ | Web client for the iManager database.Notes:If imanager-mysql is disabled, this functionality will be affected even if the third-party service is enabled or configured | ||
| deploy_disable_imanager_gateway_redis | imanager-gateway-redis | √ | √ | Database services stored in iManager gateway session | |
| iManager User Center | deploy_disable_keycloak | keycloak | √ | √ | Used for iManager user management to ensure security and unity |
| deploy_disable_keycloak_postgresql | keycloak-postgresql | √ | √ | Used for storing Keycloak's dataNotes: If keycloak is disabled, this function will be affected even if the third-party service is enabled or configured | |
| iManager Logs | deploy_disable_fluentd_es | fluentd-es | √ | iManager log collection function.Notes: If ES is disabled, log collection cannot be used even if the service is enabled | |
| deploy_disable_elasticsearch | elasticsearch | √ | iManager elasticsearch for storing logs and access statistics records | ||
| deploy_disable_kibana | kibana | √ | iManager log presentation and access statistics functions for visualizing data in ES.Note: If ES is disabled, this function will be affected even if the third-party service is enabled or configured | ||
| deploy_disable_consul_server | consul-server | √ | iManager database monitoring and automatic discovery service functions | ||
| System Monitoring | deploy_disable_prometheus | prometheus | √（Temporarily need to configure the same namespace as iManager deployment） | The monitoring system function of iManager affects resource load monitoring and operation logs. After disabling, there will be no monitoring data and operation logs | |
| deploy_disable_prometheus_node_exporter | prometheus-node-exporter | √ | Used for Kubernetes node monitoring. After disabling, the overview page will not be able to monitor memory/hard drive "usage", "used" and "total", as well as hard drive "maximum usage value", "maximum available value", and line statistics data.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 | √ | Dynamic scaling function of service nodes. After disabling, it will affect the Kubernetes resource metric monitoring.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 | √ | Used for Kubernetes status information monitoring. After disabling, the overview page will not be able to monitor CPU/memory "request values", "limit values" and other data.Notes: If prometheus is disabled, this function will be affected even if third-party services are enabled or configured | ||
| deploy_disable_blackbox_exporter | blackbox-exporter | √ | iManager URL Monitoring | ||
| deploy_disable_ssl_exporter | ssl-exporter | √（Should be deployed to the same namespace as the iManager machine） | Used for Kubernetes certificate expiration monitoring. After disabling, Kubernetes certificate expiration cannot be monitored | ||
| Analysis and Monitoring Platform | deploy_disable_grafana | grafana | √ | iManager analysis and monitoring platform. After disabling, there will be no data on the Overview and Basic Services pages | |
| deploy_disable_grafana_postgresql | grafana-database | √（The "grafana" database needs to be created manually in PostgreSQL first | Used for storing Grafana data. After disabling, there will be no data on the Overview and Basic Services pages.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 iManager. After disabling, "Log" and "Command Line" will not be available |
Notes：
When “deploy _disable _prometheus”, “deploy _disable _alert”, and “deploy _disable _blackbox _exporter” are configured as third-party services, their usage will be temporarily restricted. Please configure them carefully.