Ingress Module Release v5.1.0
Welcome to the latest release of Ingress module of SIGHUP Distribution maintained by team SIGHUP.
This release switches the nginx-ingress controller image to a custom build of the Chainguard fork, produced in-house in container-image-sync. The published tag now carries a -chainguard suffix (v1.15.5-chainguard).
This release also validates the module against Kubernetes 1.35 (added to the e2e test matrix), removes the support for Kubernetes 1.31 and bumps the packages. See the maxtrix below.
Breaking Changes 💔
The HAProxy chart bump (v3.2.4 → v3.2.8) restructured the CRD-installer Job:
- It was renamed:
haproxy-ingress-crdjob-1→haproxy-ingress-crdjob
(in dual modehaproxy-ingress-internal-crdjob-1→haproxy-ingress-internal-crdjob). - The CRD-installer now ships dedicated RBAC (
ServiceAccount,ClusterRole,
ClusterRoleBindingnamed*-crdjob), instead of reusing the controller's main
ServiceAccount.
If you patch or reference these resources by name (e.g. to add nodeSelector/
tolerations, or in GitOps/RBAC tooling), update the references to the new names.
In dual mode only the internal CRD-installer runs — the external crdjob and its
RBAC are removed, since CRDs are cluster-scoped and installing them once is enough.
Patches in dual mode must target haproxy-ingress-internal-crdjob.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
aws-cert-manager |
N.A. | No update |
aws-external-dns |
N.A. | No update |
cert-manager |
v1.20.2 |
v1.19.2 |
dual-nginx |
v1.15.5-chainguard |
v1.15.1 |
external-dns |
v0.21.0 |
v0.20.0 |
forecastle |
v1.0.159 |
No update |
haproxy |
v3.2.8 |
v3.2.4 |
nginx |
v1.15.5-chainguard |
v1.15.1 |
Please refer the individual release notes to get a more detailed information on each release.
Update Guide 🦮
Process
To upgrade this core module from v5.0.1 to v5.1.0, you need to download this new version, and apply the instructions below.
kustomize build <your-project-path> | kubectl apply -f -