Changes and Releases
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Added
- Add support for Gateway API resources
Fixed
- Disable the kubescape scanner input by default.
Added
- Add Gateway API support with HTTPRoute template (
.Values.route). - Add support for SecurityPolicy resources for authentication via Envoy Gateway.
Changed
- Make Ingress resource conditional with
.Values.ingress.enabled (defaults to true for backwards compatibility).
Fixed
- Downgrade k8s client libraries to v1.34 versions to fix a regression (#135895).
Announcements
- starboard-exporter now supports kubescape! In addition to Trivy VulnerabilityReports, starboard-exporter now also supports reconciliation of Kubescape VulnerabilityManifests. Metrics have been updated to include a
scanner label, indicating the source type of the data. Trivy and Kubescape can be used simultaneously, or individually toggled on and off. See the README for more information. - There is a breaking change to one of the CLI flags in this version. The
--vulnerability-scans-enabled flag has been renamed to --trivy-vulnerability-scans-enabled in order to facilitate the new Kubescape scanner support. Users installing via the Helm chart are not affected.
Added
- Support for Kubescape vulnerability scanning via
VulnerabilityManifest CR. - Scanner label (
scanner="trivy" or scanner="kubescape") to all vulnerability metrics to distinguish between scanning sources. - Command-line flag
--kubescape-vulnerability-scans-enabled. - Helm values configuration for enabling/disabling individual scanners under
exporter.vulnerabilityReports.scanners. - Added backwards compatibility for legacy
vulnerabilityReports.enabled Helm value (now enables Trivy scanner)
Changed
- Renamed Trivy-specific functions and constants to include “Trivy” prefix to distinguish them from Kubescape components while maintaining shared metrics.
- Command-line flag
--vulnerability-scans-enabled to --trivy-vulnerability-scans-enabled (Breaking Change).
Changed
- Move Giant Swarm specific values to the bundle chart. Clean up the aws-load-balancer-controller chart from any GS specific stuff.
- Shorten bundle chart name to
aws-lb-controller-bundle
Added
- Add additional permissions to the controller IAM role.
Changed
- Document upgrade path from v2 to v3
Fixed
- Configure the efs-csi-driver chart to use the IAM role managed by the bundle chart.