Shipped · Observability

What prometheus-operator/prometheus-operator shipped

The public repository of Prometheus-operator · github.com/prometheus-operator/prometheus-operator

Written by FoxPlug from the repository's own releases; not affiliated with Prometheus-operator. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/prometheus-operator/prometheus-operator; Prometheus-operator did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for prometheus-operator, free

Week of November 2, 2026

What shipped

Why it matters

This week brought a feature release with new CRD fields and a follow-up patch because the container images for the first release failed to publish. Users also get Probe status reconciliation for PrometheusAgent behind the feature gate, CORS origin support for Alertmanager, and a bump to Alertmanager v0.34.2.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

0.95.0 ships new CRD fields for AlertmanagerConfig file handling and extra scrape metrics; 0.95.1 republishes images after a CI publish failure. Plus CORS origin support for Alertmanager and Probe status reconciliation for PrometheusAgent.

Post for LinkedIn

This week the project published 0.95.0, adding the alertmanagerConfigFileSystemMode field to the Alertmanager CRD and extraScrapeMetrics to the Prometheus and PrometheusAgent CRDs. A 0.95.1 patch followed because the CI workflow failed to publish the 0.95.0 container images. Alertmanager users get a spec.web.corsOrigin field backed by the new web.cors.origin flag in Alertmanager v0.34.2, which is now the bundled version. The PrometheusAgent controller reconciles Probe status bindings when the StatusForConfigurationResources feature gate is on, logging errors for conflicting namespace flags was added, and dependency and tooling versions were bumped.

Week of October 26, 2026

What shipped

Why it matters

This week brings improvements to configuration propagation, status tracking, and operational flexibility. The changes enhance how alert routing works, improve observability of the operator itself, and provide better control over security-sensitive endpoints.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

New features in prometheus-operator this week: AlertmanagerConfig Route labels support, PrometheusAgent ScrapeConfig status reconciliation, ThanosRuler imagePullPolicy fixes, and --disable-pprof option for secure environments.

Post for LinkedIn

This week's prometheus-operator updates focus on operational improvements and configuration management. AlertmanagerConfig now supports route labels for fine-grained alert routing, PrometheusAgent properly reconciles ScrapeConfig status with binding management, and ThanosRuler correctly applies imagePullPolicy settings. We also added a --disable-pprof option for regulated environments and improved logging consistency across components. These changes enhance both functionality and security for Prometheus deployments.

Week of October 19, 2026

What shipped

Why it matters

This week is mostly about validation and reliability: several receiver configurations that Alertmanager would refuse to load are now rejected earlier, and duplicate time interval names are caught before they break config generation. The 0.94.2 release rebuilds base images and Go binaries to drop specific root CAs and address vulnerabilities, and the Azure SD fix keeps HTTP client settings in generated scrape configs.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Prometheus-operator 0.94.2 is out: rebuilt base images drop the Comodo AAA Services and emSign ECC Root CA - G3 root CAs, and Go 1.27.3 fixes vulnerabilities. We also tightened validation for MSTeamsV2, Webex and duplicate time interval names, and fixed Azure SD scrape config fie

Post for LinkedIn

Prometheus-operator 0.94.2 is released. The rebuild removes the Comodo AAA Services root and emSign ECC Root CA - G3 root CAs from the base images and moves to Go 1.27.3 to fix vulnerabilities. Alongside the release, validation got stricter: MSTeamsV2 receivers without a webhook URL, Webex receivers without httpConfig.authorization, and duplicate time interval names in AlertmanagerConfig are now rejected before they can break config generation. The Azure SD scrape config now writes tls_config, follow_redirects and enable_http2, and environment no longer drops auth and proxy settings.

Week of October 12, 2026

What shipped

Why it matters

This week adds a global extraScrapeMetrics setting and lets the same option be set per scrape config, which removes repetition for users who want extra scrape metrics. It also extends runtime log level configuration for newer Prometheus versions and adds validation for PagerDuty and Telegram receivers. Documentation changes clarify that ServiceMonitor targets must be backed by Pods and explain volume permissions, which addresses common sources of confusion for people deploying the operator.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: extraScrapeMetrics in the global Prometheus config and per-scrape CRDs, runtime log level for Prometheus 3.15.0+, distroless image variants, Alertmanager route labels, and PagerDuty and Telegram validation. Docs: ServiceMonitor targets must be backed by Pods.

Post for LinkedIn

This week in prometheus-operator: extraScrapeMetrics can now be set in the global Prometheus configuration and per scrape config through ServiceMonitor, PodMonitor, Probe and ScrapeConfig. The log level can be configured in the runtime config for Prometheus 3.15.0 and higher. Opt-in distroless runtime image variants were added for the operator, config reloader and admission webhook, with BusyBox images staying the default. Alertmanager secret config now supports route labels, and validation was improved for PagerDuty and Telegram receivers. Docs now note that ServiceMonitor targets must be backed by Pods and cover volume permissions for persistent storage.

Week of September 28, 2026

What shipped

Why it matters

This week brought improvements to status binding reconciliation for PrometheusAgent across ServiceMonitor and PodMonitor resources, bringing feature parity with existing Prometheus reconciliation patterns. AlertmanagerConfig also gained missing lifecycle management features including finalizers and binding cleanup. Several bug fixes and test enhancements ensure better reliability when converting and validating alerting configurations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: PrometheusAgent now reconciles ServiceMonitor and PodMonitor status bindings, AlertmanagerConfig gains finalizers and binding cleanup, and fixes for email receiver conversion. Kubernetes dependencies updated to v0.37.1.

Post for LinkedIn

Prometheus-operator this week: PrometheusAgent now fully reconciles ServiceMonitor and PodMonitor status bindings with proper cleanup, AlertmanagerConfig implements the missing finalizer and binding garbage collection pattern, email receiver conversion webhook issues resolved, and Telegram botToken support added to Alertmanager global config. Kubernetes dependencies updated to v0.37.1.

Week of September 21, 2026

What shipped

Why it matters

Version 0.94.1 fixes critical RBAC issues that affected finalizer operations and makes permissions more restrictive. Several validation improvements for remote write and receiver configurations enhance reliability and security of alerting configurations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Prometheus-operator 0.94.1 is out. This release fixes RBAC permissions for finalizers and continues improving validation for alerting receivers and remote write configurations.

Post for LinkedIn

Prometheus-operator 0.94.1 is now available. This release addresses RBAC permission scoping for the operator service account, fixes ThanosRuler remote-write field filtering, and adds URL validation for alerting receivers. Updates include improved status handling for AlertmanagerConfigs and enhanced permission controls based on repair policies.

Week of September 14, 2026

What shipped

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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.

Post for LinkedIn

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.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.