Skip to content
QuenchWorks

apisix-ingress-controller

Image · Gateway · standard · v2.2.0

D 3cosign signedSPDX SBOMSLSA provenanceamd64 · arm64Rebuilt 2026-08-20

The Apache APISIX Ingress Controller, the Kubernetes operator that drives an APISIX data plane. Reconciles Gateway API resources, native Ingress and APISIX's own CRDs such as ApisixRoute, ApisixUpstream and ApisixPluginConfig into APISIX configuration. Built from the ASF source release; tracks Gateway API 1.6 and needs Kubernetes 1.31 or newer.

Current digest (deployed by the chart)

sha256:ddde66c228afa4e945716c81f67ad1baa16370540c60f5dc0c2d84dea7166756

Signatures, the SBOM, and provenance all attach to this digest. Pin to it for reproducible, tamper-evident pulls.

Signed
cosign keyless
SBOM
SPDX, on digest
Provenance
SLSA build
Architectures
amd64, arm64
Runs as
nonroot (uid 1001)
Root filesystem
read-only
Image size
18.2 MB

Published versions

1 tag

Each tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.

VersionSizePublishedDigest
2.2.0latest18.2 MB2026-08-20sha256:ddde66c228af…

Security report (Trivy)

D· 61/1003 fixable · rebuild clears them

Vulnerability detail

apisix-ingress-controller 2.2.0 · 3 CVE
CVESeverityPackageInstalledFixed inTitle
CVE-2026-84304HIGHgoogle.golang.org/grpcv1.82.11.83.1gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, in ...
CVE-2026-84445HIGHgoogle.golang.org/grpcv1.82.11.82.2, 1.83.2, 1.85.0-dev.0.20260825072537-93e31b48545egRPC-Go xDS servers: Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers
CVE-2026-84303MEDIUMgoogle.golang.org/grpcv1.82.11.83.1gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, th ...
0
Critical
2
High
1
Medium
0
Low
0
Unknown

Pull the image

Run it directly with Docker, Podman, or any Kubernetes workload. Nonroot, read-only root filesystem, built for amd64 and arm64.

Pull (tag)

docker pull ghcr.io/quenchworks/images/apisix-ingress-controller:2.2.0

Pinned by digest (recommended)

docker pull ghcr.io/quenchworks/images/apisix-ingress-controller@sha256:ddde66c228afa4e945716c81f67ad1baa16370540c60f5dc0c2d84dea7166756

Tags

2.2.02.2.0-amd642.2.0-arm64

Images are tagged by app version (never :latest): a multi-arch index plus per-arch tags.

App version
2.2.0
Architectures
amd64, arm64
Runs as
nonroot (uid 1001)
Root filesystem
read-only
License
Apache-2.0

Verify the supply chain

This image is cosign-signed and carries an SPDX SBOM and a SLSA build-provenance attestation on the same digest. Check all three yourself:

# 1. signature — built and signed by QuenchWorks CI
cosign verify ghcr.io/quenchworks/images/apisix-ingress-controller:2.2.0 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# 2. SLSA build provenance — which workflow built it, from what
cosign verify-attestation --type https://slsa.dev/provenance/v1 ghcr.io/quenchworks/images/apisix-ingress-controller:2.2.0 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# 3. SPDX SBOM — the package inventory
cosign verify-attestation --type https://spdx.dev/Document/v2.3 ghcr.io/quenchworks/images/apisix-ingress-controller:2.2.0 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

See the SBOM & provenance guide for reading the SBOM and using these checks in CI.

Transparency

Every image carries its SBOM and provenance as attestations on the same digest, publicly verifiable with the commands above (they check the package and the Sigstore transparency log, Rekor).

Upstream project: https://apisix.apache.org/docs/ingress-controller/overview/