Start with troubleshooting
Check runtime phase, operator logs, gateway route registration, KEDA status, and Kubernetes events before opening a support request.
Troubleshooting docsSupport
XTrinode Support
For support requests, include the XTrinode version, Kubernetes version, cloud provider, deployment path, affected custom resources, gateway/API/operator observations, and relevant events or logs.
Verify the platform path
Confirm namespaces, CRDs, Helm releases, image registry access, and provider IAM before debugging individual runtimes.
Deployment docsTrack planned improvements
The checked-in enhancement backlog covers cloud parity, lifecycle reliability, security boundaries, connectors, tools, and operability.
Enhancement backlogFurther enhancements
This backlog summarizes current enhancement themes for the open-source project. It is a support-oriented snapshot, not a promise of release order.
Keep the API server internal by default
Document the API server as an internal control-plane service, keep gateway resume calls on scoped tokens, and define the requirements before any exposed-mode design.
Open GitHub issuesAdd interrupted cleanup coverage
Add live-cluster interruption tests for route registration, route cleanup, KEDA handoff, suspend/resume retries, leases, and stale lifecycle annotations.
Open GitHub issuesBring AWS and Azure closer to GCP parity
GCP/GKE/CAPG is the fully exercised cloud path. AWS/EKS/CAPA and Azure/AKS/CAPZ need equivalent live deploy, routing, KEDA, and managed node-pool validation.
Open GitHub issuesComplete typed connector validation
Audit typed connector properties against the pinned Trino version, settle connector field semantics, and document each connector as validated, partial, or custom-only.
Open GitHub issuesExpand real-Trino connector coverage
PostgreSQL and Iceberg have live coverage today. The next matrix should add more connector fixtures and validate successful queries plus expected runtime errors.
Open GitHub issuesAdd an operator-facing Gateway UI
Expose route inventory, routing groups, backend state, health, resume attempts, and request counters without becoming a SQL console or secret surface.
Open GitHub issuesVerify generated artifacts beyond CRDs
Extend generated-output checks to deepcopy code, CRDs, RBAC, Helm dependency locks, and selected rendered templates so API and packaging drift is caught earlier.
Open GitHub issuesAdd xtrinodectl for day-two workflows
Provide a thin operational CLI for runtime inventory, describe, wait, suspend, resume, route lookup, catalog inspection, and support bundles over existing control boundaries.
Open GitHub issuesScope a read-only MCP interface
Design a narrow operator-facing MCP surface for runtime, route, catalog, and validation posture inspection without exposing secrets or creating a second control plane.
Open GitHub issuesReview resource-groups chart alignment
Compare resource-groups rendering against the pinned upstream Trino chart and add tests for ConfigMaps, mounts, revision behavior, and documented divergence.
Open GitHub issuesSplit the largest handwritten Go files
Decompose controller, Trino resource builder, and gateway service code along existing domain boundaries while preserving behavior and test coverage.
Open GitHub issuesImprove drain and lease operability
Explore query-aware drain completion, drain metrics, lease dashboards, and carefully audited emergency state override design.
Open GitHub issues