What prometheus-operator/prometheus-operator shipped
Generated by FoxPlug from public activity — not affiliated with Prometheus-operator.
Week of September 14, 2026
What shipped
- Event 3: Topology sharding now reports unbalanced configurations in the Reconciled condition when the number of shards is not a multiple of the number of zones. Pull request #8670
- Event 0: Added govulncheck workflow to detect vulnerabilities in dependencies. Pull request #8824
- Event 1: Enabled unused and whitespace linters in the golangci-lint configuration. Pull request #8827
- Event 2: Added test verification for TLS connections to Alertmanager. Pull request #8821
- Event 4: Fixed grammar in PrometheusRule developer documentation. Pull request #8817
Why it matters
The week focused on improving code quality and testing coverage. Topology sharding now provides better visibility into configuration issues, while new linting checks and vulnerability scanning help catch problems earlier in development.
Changelog entry
- Topology sharding now reports unbalanced configurations in Reconciled condition when shards is not a multiple of zone count Pull request #8670
- Added govulncheck workflow for vulnerability detection Pull request #8824
- Enabled unused and whitespace linters in golangci-lint Pull request #8827
- Added TLS connection verification tests for Alertmanager Pull request #8821
This week: topology sharding reports unbalanced configurations, govulncheck workflow added for vulnerability detection, unused and whitespace linters enabled, TLS connection tests for Alertmanager, and documentation grammar fixes.
This week in prometheus-operator: Topology sharding now reports unbalanced configurations in the Reconciled condition when shard counts don't align with zone counts. We added govulncheck workflow for vulnerability detection and enabled additional linters for code quality. TLS connection verification tests for Alertmanager were introduced, and documentation improvements continue.