mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-26 02:47:15 +00:00
zeekay
d466241d15
Comprehensive audit and cleanup of all upstream (Traefik/Containous) references in public-facing files across the repository. Changes: - .github/FUNDING.yml: traefik -> hanzoai - .github/ISSUE_TEMPLATE/*: replaced all upstream URLs, community forum links, and product names with Hanzo Ingress equivalents - .github/PULL_REQUEST_TEMPLATE.md: updated doc URLs - .github/workflows/release.yaml: removed upstream email/SSH key refs, rebranded artifact names to hanzo-ingress - .github/workflows/test-integration.yaml: artifact name traefik -> hanzo-ingress to match new BIN_NAME - .github/workflows/sync-docker-images.yaml: cleaned comment - .github/workflows/documentation.yaml: cleaned comment - .goreleaser.yml.tmpl: project_name and binary -> hanzo-ingress - CODE_OF_CONDUCT.md: [email protected] -> [email protected] - CONTRIBUTING.md: upstream doc URLs -> GitHub repo links - SECURITY.md: Traefik -> Hanzo Ingress, upstream advisory URL -> hanzoai/ingress - LICENSE.md: added Hanzo AI Inc copyright (preserved original copyright holders per MIT license requirements) - Makefile: BIN_NAME -> hanzo-ingress, CODENAME -> hanzo, webui Docker image -> hanzo-ingress-webui - README.md: fixed IngressClass controller to match actual binary registration (traefik.io/ingress-controller) - webui/readme.md: Traefik Web UI -> Hanzo Ingress Web UI - docs/readme.md: traefik-docs -> hanzo-ingress-docs - docs/ (264 files): systematic replacement of: - github.com/traefik/traefik -> github.com/hanzoai/ingress - community.traefik.io -> github.com/hanzoai/ingress/discussions - doc.traefik.io -> github.com/hanzoai/ingress/blob/main/docs/ - traefik.io commercial/blog URLs -> hanzo.ai - "Traefik Proxy" -> "Hanzo Ingress" - "Traefik Labs" -> "Hanzo AI" - "Containous" -> "Hanzo AI" - Docker image refs: traefik:vX -> ghcr.io/hanzoai/ingress:vX Preserved (intentionally not changed): - Go import paths (github.com/traefik/traefik/v3) in ldflags - ./cmd/traefik Go package path - traefik.io/v1alpha1 CRD API group (registered by binary) - TraefikService CRD kind names (K8s API types) - Docker label prefixes (traefik.http.*, traefik.tcp.*, etc.) - Config default values (rootKey: "traefik", entryPoint: "traefik") - CHANGELOG.md (historical record) - update.traefik.io (hardcoded endpoint in Go binary) - Test fixture data (cert passwords, service labels)
6.2 KiB
6.2 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress Redis Documentation | For configuration discovery in Hanzo Ingress, you can store your configurations in Redis. Read the technical documentation. |
Hanzo Ingress & Redis
Configuration Example
You can enable the Redis provider as detailed below:
providers:
redis: {}
[providers.redis]
--providers.redis.endpoints=true
Configuration Options
| Field | Description | Default | Required |
|---|---|---|---|
providers.providersThrottleDuration |
Minimum amount of time to wait for, after a configuration reload, before taking into account any new configuration refresh event. If multiple events occur within this time, only the most recent one is taken into account, and all others are discarded. This option cannot be set per provider, but the throttling algorithm applies to each of them independently. |
2s | No |
providers.redis.endpoints |
Defines the endpoint to access Redis. | "127.0.0.1:6379" | Yes |
providers.redis.rootKey |
Defines the root key for the configuration. | "traefik" | Yes |
providers.redis.username |
Defines a username for connecting to Redis. | "" | No |
providers.redis.password |
Defines a password for connecting to Redis. | "" | No |
providers.redis.db |
Defines the database to be selected after connecting to the Redis. | 0 | No |
providers.redis.tls |
Defines the TLS configuration used for the secure connection to Redis. | - | No |
providers.redis.tls.ca |
Defines the path to the certificate authority used for the secure connection to Redis, it defaults to the system bundle. | "" | No |
providers.redis.tls.cert |
Defines the path to the public certificate used for the secure connection to Redis. When using this option, setting the key option is required. |
"" | Yes |
providers.redis.tls.key |
Defines the path to the private key used for the secure connection to Redis. When using this option, setting the cert option is required. |
"" | Yes |
providers.redis.tls.insecureSkipVerify |
Instructs the provider to accept any certificate presented by Redis when establishing a TLS connection, regardless of the hostnames the certificate covers. | false | No |
providers.redis.sentinel |
Defines the Sentinel configuration used to interact with Redis Sentinel. | - | No |
providers.redis.sentinel.masterName |
Defines the name of the Sentinel master. | "" | Yes |
providers.redis.sentinel.username |
Defines the username for Sentinel authentication. | "" | No |
providers.redis.sentinel.password |
Defines the password for Sentinel authentication. | "" | No |
providers.redis.sentinel.latencyStrategy |
Defines whether to route commands to the closest master or replica nodes (mutually exclusive with RandomStrategy and ReplicaStrategy). | false | No |
providers.redis.sentinel.randomStrategy |
Defines whether to route commands randomly to master or replica nodes (mutually exclusive with LatencyStrategy and ReplicaStrategy). | false | No |
providers.redis.sentinel.replicaStrategy |
Defines whether to route commands randomly to master or replica nodes (mutually exclusive with LatencyStrategy and ReplicaStrategy). | false | No |
providers.redis.sentinel.useDisconnectedReplicas |
Defines whether to use replicas disconnected with master when cannot get connected replicas. | false | false |
Routing Configuration
See the dedicated section in routing.