What Data for This Category Looks Like
Data for this category comes primarily from Kubernetes API, image registries, monitoring systems, and CI pipelines. Daily outputs include cluster change orders, namespace quota tables, deployment records, fault reports, and similar documents. Updates trigger when cluster changes occur. Cluster status and operational action records sync daily. Fields include cluster node identifiers, namespace quota values, Pod running status, image version numbers, and more. There are no unified fixed units, and some fields shift dynamically based on cluster scale.
What Constraints These Characteristics Impose on Deployment and Upgrade Workflows
Data sources depend on permission configurations for Kubernetes API and CI pipelines. Enable corresponding interface access permissions during deployment to avoid failing to pull cluster status or images due to insufficient permissions. Document structures are spread across multiple operations and maintenance tools. During upgrades, synchronize updates to associated fields of deployment records and change orders to maintain consistency across the operational and maintenance workflow. Update frequency ties to change triggers. During deployment, verify resource quotas and Pod status after each change to prevent resource preemption or business interruptions from configuration deviations.
How to Configure Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@cluster-host:27017/fastgpt?authSource=admin | Connects to FastGPT's built-in knowledge base and ticket storage, must match the database address and authentication details deployed on the container platform |
REDIS_URL | redis://:cache-password@redis-host:6379/0 | Caches cluster status, ticket context, and query results, must align with the container platform's cache service deployment configuration |
FE_DOMAIN | https://your-cluster-fastgpt-domain.com | Sets the official frontend access domain, used for service exposure and HTTPS protocol support within the container platform |
DB_MAX_LINK | 100–200 connections | Supports concurrent access by multiple Pods on the container platform, prevents database blocking from overly high connection counts |
ROOT_KEY | Generated per container platform operations and maintenance key management rules | Manages FastGPT super permissions, must match the cluster's key management service to avoid permission leaks |
Three Common Misconfigurations
- Certificate invalid errors or failed HTTPS redirects when accessing the page. This occurs when
FE_DOMAINis not configured in HTTPS format, and no SSL certificate is bound in the container platform Ingress configuration. - Ticket Q&A fails to pull images after a cluster upgrade. This occurs when image registry access permission configurations are not updated synchronously, preventing FastGPT from pulling the required image version from the registry.
- Frequent database connection timeouts. This occurs when
DB_MAX_LINKis set too low, failing to support concurrent database access by multiple Pods on the container platform.
How to Verify Successful Configuration
- Access the configured
FE_DOMAINaddress, confirm the page loads normally and the address bar displays the HTTPS protocol. - Navigate to the system settings page of FastGPT v4.17.0, check that database and cache connection statuses show normal.
- Run a small-scale cluster change test, confirm FastGPT can pull cluster status and generate corresponding operation and maintenance tickets.
- Check the container platform's monitoring system, confirm FastGPT Pods run normally with no abnormal restarts or excessive resource usage.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.