Sealane v1.7.0¶
A port check in the analysis, and the create-from-Service template gets the right port¶
Highlights¶
- Destination port check. The mesh analysis now reports
vs-port-not-exposed(error) when a VirtualService destination names aport.numberthe Service does not expose — the case where Envoy answers 503 while every resource looks valid. The route check already flagged it for one request; the analysis catches it for every route, with the finding link opening the offending field. - Right port from the Service page. "New VirtualService for this service" now fills the route destination with the Service's port instead of the template's 80, so the created route works on first apply.
- Translated kickers. The small page labels ("Mesh analysis", "Request workbench", …) and the analysis namespace label follow the UI language.
These came out of a first-use walkthrough on a live cluster: create a VirtualService from a Service page → check a request → read the analysis → fix the finding. The loop works; the port was the one thing it got wrong.
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.7.0 -n <namespace> --reset-then-reuse-values
Install¶
helm install sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.7.0 -n sealane --create-namespace
# or
kubectl apply -f https://github.com/wonjune95/sealane/releases/download/v1.7.0/install.yaml
ghcr.io/wonjune95/sealane:1.7.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.6.0...v1.7.0