How trinodb/charts works
Main Components
• Helm Charts Repository:
• Two primary charts are included: one for Trino (“charts/trino”) and one for Trino Gateway (“charts/gateway”).
• Each chart contains its own Chart.yaml, templated Kubernetes manifest files (e.g., deployments, services, ingress, autoscalers, configmaps, secrets), and specific configuration (values.yaml).
• CI/CD & Testing Infrastructure:
• Under .github/workflows you have the “ci-cd.yaml” manifest, which indicates an automated pipeline to build, test, and release these charts.
• The tests directory houses YAML files and shell scripts used for validating the charts in a Kubernetes cluster (via kind and chart-testing).
• Development Tools & Hooks:
• Pre-commit hooks (e.g., .pre-commit-config.yaml) and release configuration files show additional automation aspects that ensure documentation and code quality.
Relationships and Interactions
• For Trino: Deployment objects for the coordinator, worker, autoscaling configurations, and associated configuration (configmaps, secrets).
• For Trino Gateway: Deployment, ingress, services, and any authentication secrets.
• The flow from the Helm installation command (from the command line or CI pipeline) to the creation of Kubernetes resources.
• The testing process: how test scripts (in tests/) validate the deployments once helm templates are applied.
• CI/CD pipelines triggering build, helm lint checks, tests, and eventual deployments or chart packaging in the GitHub workflows.
Architectural Patterns
• That the charts follow a declarative deployment model. The chart templates use Helm’s templating engine to dynamically generate Kubernetes YAML.
• Separation of concerns is evident: each chart contains its own set of configurations and Kubernetes resources to support independent scaling and management (e.g., the Trino backend vs. Trino Gateway fronting the system).
• Use a modular approach to highlight that while both charts interact by being deployed on the same cluster, they serve different roles in the Trino ecosystem.
Specify Relevant Technologies and Tools
• Kubernetes: The target platform for all the deployments.
• Helm: The package manager used to install and manage these charts.
• CI/CD – GitHub Actions are used to test and release the charts.
• Testing tools: kind (for local clusters) and chart-testing for validating deployments.
• Pre-commit hooks help maintain code quality and documentation consistency.