mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-26 02:47:15 +00:00
zeekay
ac48b442f1
Production runs exactly three providers — Kubernetes Ingress, Kubernetes CRD
and File. Everything else was inherited from upstream and carried forward
untouched: Docker, Swarm, Consul Catalog, and the KV config backends, plus
their docs, integration fixtures and compose files.
Removes 111 files across docs/content/{providers,routing,reference,user-guides,
expose}, integration/{resources/compose,fixtures/consul_catalog} and
pkg/config/kv, and updates the README to state the three supported providers
rather than upstream's full matrix.
Dead surface is not free: it is documentation that describes behaviour nobody
here can exercise, integration fixtures that shape CI time, and config code
that has to keep compiling through every refactor.
Verified: go build ./... exits 0 and go vet is clean after the deletions —
pkg/config/kv had no remaining importers.
715 B
715 B
title, description
| title | description |
|---|---|
| Getting Started with Hanzo Ingress | Quick start guides for deploying Hanzo Ingress in Kubernetes and Docker environments |
Getting Started with Hanzo Ingress
Hanzo Ingress can be deployed in various environments. Choose your preferred deployment method:
- Kubernetes Quick Start - Deploy Hanzo Ingress using Helm
Each guide will help you:
- Install Hanzo Ingress
- Expose the dashboard
- Deploy a sample application
- Configure basic routing
Before You Begin
Make sure you have the necessary prerequisites for your chosen environment:
- Kubernetes: A running Kubernetes cluster, Helm 3, and kubectl
- Docker: Docker and optionally Docker Compose