How apache/apisix-helm-chart works
Project type and purpose
• This is an infrastructure-as-code project made up of Helm charts for Kubernetes. Its purpose is to deploy and configure:
• Apache APISIX (the API gateway and etcd)
• APISIX Dashboard (the web UI and Admin API)
• APISIX Ingress Controller (CRDs and controller pods)
• You’re not drawing application code or business logic. Instead you’re illustrating how Helm packages turn into running K8s resources and how those resources interact at runtime.
File structure
• Top-level:
• charts/ – three sub-charts (apisix, apisix-dashboard, apisix-ingress-controller)
• docs/, test/, CI workflows, Makefile
• Each chart has:
• Chart.yaml, values.yaml (public interface)
• templates/ (Kubernetes YAML resources: Deployments, Services, ConfigMaps, Ingress, CRDs)
• crds/ in the ingress-controller chart
• The presence of CRDs and templates signals a custom-resource-based controller pattern.
README
• Confirms three deliverables (APISIX, Dashboard, Ingress Controller), compatibility matrix, usage link.
Detail
• Don’t group everything into “APISIX”. Break out etcd, gateway, admin API, Dashboard UI, Ingress Controller.
• CRDs (ApisixRoute, PluginConfig, etc.) as a separate layer.
• Test harness (kind cluster) only if needed to illustrate pipeline, otherwise omit.
• Helm lifecycles: chart fetch → template → apply → release hooks.