INFINI Gateway supports dynamic configuration loading, which allows individual instances to reload settings without restart. However, managing multiple Gateway deployments across different servers becomes time-consuming when manual file edits are required for each node.
INFINI Console provides a unified management interface for this purpose. After registering Gateway instances with Console, administrators can view, modify, and distribute configurations directly from the web interface.
Configuration Storage Requirements
The management system stores distributed configurations in Console's system index. The following API call creates a configuration entry that can be pushed to Gateway instances:
PUT .infini_configs/_doc/gateway_http_yml
{
"payload": {
"content": """
entry:
- name: elasticsearch_entry
enabled: true
router: default_router
max_concurrency: 150000
network:
binding: 0.0.0.0:8000
flow:
- name: ingestion_flow
filter:
- http:
schema: https
host: 192.168.1.50:9200
router:
- name: default_router
default_flow: ingestion_flow""",
"version": 2,
"name": "gateway_http.yml"
},
"metadata": {
"labels": {
"instance": "_all"
},
"category": "app_settings",
"name": "gateway"
},
"id": "gateway_http_yml"
}
| Field | Required | Description |
|---|---|---|
| payload.content | Yes | Raw Gateway configuration content |
| payload.version | Yes | Version number for sync validation |
| payload.name | Yes | Target filename after distribution |
| metadata.labels | Yes | Targeting labels; _all applies to all instances |
| metadata.category | Yes | Configuration category; use app_settings for Gateway |
| metadata.name | Yes | Application type: gateway or agent |
| id | Yes | Unique configuration identifier |
Gateway Connection Setup
Configure the Gateway to connect to the management server by modifying the configuration file:
env:
CONFIG_SERVER: http://192.168.1.50:9000
path.data: data
path.logs: log
path.configs: config
configs:
auto_reload: true
managed: true
panic_on_config_error: false
interval: "10s"
servers:
- $[[env.CONFIG_SERVER]]
soft_delete: false
max_backup_files: 5
api:
enabled: true
network:
binding: 0.0.0.0:2900
The managed: true flag enables remote configuration management, while auto_reload: true ensures Gateway picks up changes automatically without manual intervention.
Deployment Steps
- Create the configuration directory
mkdir config
./gateway-linux-amd64
-
Verify successful registration by checking the startup logs. The Gateway should connect to the management server and download the assigned configuration file.
-
Access the configuration management page in Console to review the deployed settings.
-
Make necessary adjustments through the UI and click Save to distribute changes. Remember to increment the version number in the configuration payload when updating settings.
-
The Gateway log output confirms successful synchronization and application of the new configuration.