mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-20 15:07:40 +00:00
zeekayandHanzo Dev
15d100931d
Hanzo CI/CD / cicd (push) Failing after 9m46s
CI/CD / cicd (push) Failing after 10m4s
Most of it was stale, not cosmetic: the docs taught `TRAEFIK_*` env, `traefik.http.*` labels, `traefik.ingress.kubernetes.io/` annotations, `.traefik.yml` plugins and `traefik_*` metrics. This binary answers to `INGRESS_*`, `ingress.http.*`, `ingress.kubernetes.io/`, `.ingress.yml` and `ingress.*` — a reader following the old text configured nothing. Two were worse than stale. Gateway API examples gave `group: traefik.io` for an IngressService backendRef, which kubernetes.go:1265 refuses against hanzo.ai. The contributing guide built with `github.com/traefik/ingress` ldflags against a module that is `github.com/hanzoai/ingress/v3`. script/code-gen.sh globs `hanzo.ai_*.yaml` and matched nothing — the per-CRD dumps had been deleted and never regenerated, so `cat` failed the script under `set -e`. controller-gen v0.19.0 restores all ten; they concatenate byte-for-byte into the committed definition and fixture. CHANGELOG.md is untouched: 6,789 lines of imported release history, where a rewrite would falsify the record rather than rebrand it. `@traefiklabs/faency`, `traefik/whoami`, k3s's `--disable=traefik`, the `traefik.io` CRD group and the MIT attribution stay — upstream's addresses, not our brand. Co-authored-by: Hanzo Dev <[email protected]>
24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
---
|
|
title: "Hanzo Ingress HTTPS & TLS Overview |Hanzo Ingress Docs"
|
|
description: "Hanzo Ingress supports HTTPS & TLS, which concerns roughly two parts of the configuration: routers, and the TLS connection. Read the documentation to learn more."
|
|
---
|
|
|
|
# HTTPS & TLS
|
|
|
|
Overview
|
|
{: .subtitle }
|
|
|
|
Hanzo Ingress supports HTTPS & TLS, which concerns roughly two parts of the configuration:
|
|
routers, and the TLS connection (and its underlying certificates).
|
|
|
|
When a router has to handle HTTPS traffic,
|
|
it should be specified with a `tls` field of the router definition.
|
|
See the TLS section of the [routers documentation](../routing/routers/index.md#tls).
|
|
|
|
The next sections of this documentation explain how to configure the TLS connection itself.
|
|
That is to say, how to obtain [TLS certificates](./tls.md#certificates-definition):
|
|
either through a definition in the dynamic configuration, or through [Let's Encrypt](./acme.md) (ACME).
|
|
And how to configure [TLS options](./tls.md#tls-options), and [certificates stores](./tls.md#certificates-stores).
|
|
|
|
{% include-markdown "includes/ingress-for-business-applications.md" %}
|