This is an automated email from the ASF dual-hosted git repository.
squakez pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/main by this push:
new 2e6d0fbcd Fix #6780: Document NetworkPolicy for operator metrics
2e6d0fbcd is described below
commit 2e6d0fbcdbcdfc35f3180cded4d3952eb904afff
Author: jjj-n <[email protected]>
AuthorDate: Fri Aug 28 15:42:51 2026 +0800
Fix #6780: Document NetworkPolicy for operator metrics
---
docs/modules/ROOT/pages/observability/monitoring/operator.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/modules/ROOT/pages/observability/monitoring/operator.adoc
b/docs/modules/ROOT/pages/observability/monitoring/operator.adoc
index a671eeb0a..bff7df586 100644
--- a/docs/modules/ROOT/pages/observability/monitoring/operator.adoc
+++ b/docs/modules/ROOT/pages/observability/monitoring/operator.adoc
@@ -19,6 +19,8 @@ kubectl apply -k
github.com/apache/camel-k/install/base/config/prometheus?ref=v{
NOTE: change the ref value with the installation version tag you want to
install.
+IMPORTANT: The provided Prometheus configuration does not create a
`NetworkPolicy`. As a post-installation step, cluster administrators should
https://kubernetes.io/docs/concepts/services-networking/network-policies/[configure
a network policy] that only allows the Prometheus scraper to access the
operator metrics port. Adapt the namespace and pod selectors to your Prometheus
deployment, and verify that the cluster networking solution supports
`NetworkPolicy` resources.
+
However, most of the time you want to probably configure and add different
thresholds and KPIs in order to monitor in a properly manner your installation.
[[metrics]]
