Skip to content

Sealane v1.8.0

The Gateway API walkthrough: a port check for HTTPRoutes and create-from-Service for them

Highlights

  • HTTPRoute backend port check. The analysis reports httproute-port-not-exposed (error) when a backendRefs port is not one of the Service's ports. Istio marks such a route ResolvedRefs=True and then answers 503, so nothing else tells you; the finding opens the offending field.
  • New HTTPRoute from the Service page. Next to the VirtualService and DestinationRule buttons, admins and editors on a cluster with the Gateway API CRDs get New HTTPRoute for this service: the editor opens with the backendRef name and port filled in, and the parent Gateway picked from the form's list. The VirtualService/DestinationRule buttons now show whenever the Istio CRDs are installed, independently of the Gateway API ones.

These came out of walking the Gateway API path on a live cluster the way the 1.7.0 release walked the Istio one (create a route for a Service, check a request, read the analysis), plus a viewer-role tour, which needed no change.

Upgrade notes

  • No breaking changes; existing sessions stay valid. The chart is unchanged apart from the version.
  • helm upgrade sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.8.0 -n <namespace> --reset-then-reuse-values

Install

helm install sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.8.0 -n sealane --create-namespace
# or
kubectl apply -f https://github.com/wonjune95/sealane/releases/download/v1.8.0/install.yaml
Image ghcr.io/wonjune95/sealane:1.8.0 (linux/amd64, linux/arm64) and the chart are signed with cosign (keyless); the SBOM is attached below.

Full Changelog: https://github.com/wonjune95/sealane/compare/v1.7.0...v1.8.0