---
source: https://iinventedlight.com/library/notes/kubernetes-ingress.md
title: "Kubernetes Ingress"
license: CC-BY-4.0
license_url: https://creativecommons.org/licenses/by/4.0/
source_license: "CC BY 4.0 (kubernetes/website); prose restates cited source lines"
attribution: "Summary by iinventedlight (AI-assisted). Sources: Kubernetes Authors, Ingress, CC BY 4.0 (kubernetes/website); Kubernetes Authors, Ingress Controllers, CC BY 4.0 (kubernetes/website)."
author: "iinventedlight (synthesis of cited sources); text drafted with AI assistance"
date: 2026-11-04
status: published
checked_on: 2026-11-04
as_of: 2026-11-04
confidence: medium
untested: "No code was run for this note; only the fetched documentation pages were read."
category: coding-references
topic_area: "code-ai-eng: Kubernetes"
tags: ['kubernetes', 'ingress', 'networking', 'http']
sources:
  - id: S1
    title: "Ingress"
    publisher: Kubernetes Authors
    url: https://kubernetes.io/docs/concepts/services-networking/ingress/
    accessed: 2026-11-04
    license: "CC BY 4.0 (kubernetes/website)"
  - id: S2
    title: "Ingress Controllers"
    publisher: Kubernetes Authors
    url: https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/
    accessed: 2026-11-04
    license: "CC BY 4.0 (kubernetes/website)"
---
# Kubernetes Ingress

**Answer:** An Ingress routes external HTTP and HTTPS traffic to Services inside a cluster using rules based on hostnames and paths. It can also provide load balancing, TLS termination and name-based virtual hosting. It only works if an ingress controller, such as ingress-nginx or a cloud provider's, is running. The Ingress API is frozen; new features go to the Gateway API.

## Example

```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata: {name: web}
spec:
  ingressClassName: nginx
  tls:
  - hosts: [example.com]
    secretName: example-tls
  rules:
  - host: example.com
    http:
      paths:
      - path: /api
        pathType: Prefix
        backend: {service: {name: api, port: {number: 80}}}
```

## Limits

- HTTP and HTTPS only; other protocols use Services of type NodePort or LoadBalancer.
- Review the documentation for your choice of ingress controller to learn which annotations are expected and / or supported. (S1)

## Choosing a controller

Kubernetes docs list many controllers (cloud gateways, NGINX, Envoy-based and others).

## Claims
- id: C1
  claim: Ingress may provide load balancing, SSL termination and name-based virtual hosting.
  source: S1
  evidence: "Ingress may provide load balancing, SSL termination and name-based virtual hosting."
- id: C2
  claim: The Ingress API has been frozen.
  source: S1
  evidence: "The Ingress API has been frozen."
- id: C3
  claim: An Ingress does not expose arbitrary ports or protocols.
  source: S1
  evidence: "An Ingress does not expose arbitrary ports or protocols."
- id: C4
  claim: An ingress controller must be running for an Ingress to work.
  source: S2
  evidence: "In order for an Ingress to work in your cluster, there must be an ingress"

## Sources
- [S1] Ingress. Kubernetes Authors. https://kubernetes.io/docs/concepts/services-networking/ingress/ . License: CC BY 4.0 (kubernetes/website). Accessed 2026-11-04.
- [S2] Ingress Controllers. Kubernetes Authors. https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/ . License: CC BY 4.0 (kubernetes/website). Accessed 2026-11-04.

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).