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 bc65b4b60 fix(doc): missing links
bc65b4b60 is described below
commit bc65b4b608623acacc24128c992e7b1f1c6983c5
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Thu Jun 18 08:50:42 2026 +0200
fix(doc): missing links
---
docs/modules/ROOT/pages/observability/monitoring.adoc | 5 -----
docs/modules/ROOT/pages/scaling/integration.adoc | 2 +-
docs/modules/traits/pages/builder.adoc | 2 +-
3 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/docs/modules/ROOT/pages/observability/monitoring.adoc
b/docs/modules/ROOT/pages/observability/monitoring.adoc
index 24c2f7e56..4b5b96fa8 100644
--- a/docs/modules/ROOT/pages/observability/monitoring.adoc
+++ b/docs/modules/ROOT/pages/observability/monitoring.adoc
@@ -44,8 +44,3 @@ EOF
----
By default, the Prometheus instance discovers applications to be monitored in
the same namespace. You can use the `podMonitorNamespaceSelector` field from
the `Prometheus` resource to enable cross-namespace monitoring. You may also
need to specify a ServiceAccount with the `serviceAccountName` field, that's
bound to a Role with the necessary permissions.
-
-=== What's Next
-
-- xref:observability/monitoring/operator.adoc[Camel K operator monitoring]
-- xref:observability/monitoring/integration.adoc[Camel K integration
monitoring]
diff --git a/docs/modules/ROOT/pages/scaling/integration.adoc
b/docs/modules/ROOT/pages/scaling/integration.adoc
index b358fb977..e04fcaedf 100644
--- a/docs/modules/ROOT/pages/scaling/integration.adoc
+++ b/docs/modules/ROOT/pages/scaling/integration.adoc
@@ -133,7 +133,7 @@ For example, executing the following command creates an
_autoscaler_ for the Int
$ kubectl autoscale it <integration_name> --min=2 --max=5 --cpu-percent=80
----
-xref:observability/monitoring/integration.adoc[Integration metrics] can also
be exported for horizontal pod autoscaling (HPA), using the
https://github.com/DirectXMan12/k8s-prometheus-adapter[custom metrics
Prometheus adapter], so that the Integration can scale automatically based on
its own metrics.
+Integration metrics can also be exported for horizontal pod autoscaling (HPA),
using the https://github.com/DirectXMan12/k8s-prometheus-adapter[custom metrics
Prometheus adapter], so that the Integration can scale automatically based on
its own metrics.
If you have an OpenShift cluster, you can follow
https://docs.openshift.com/container-platform/4.4/monitoring/exposing-custom-application-metrics-for-autoscaling.html[Exposing
custom application metrics for autoscaling] to set it up.
diff --git a/docs/modules/traits/pages/builder.adoc
b/docs/modules/traits/pages/builder.adoc
index 01b7029bd..4701b1412 100755
--- a/docs/modules/traits/pages/builder.adoc
+++ b/docs/modules/traits/pages/builder.adoc
@@ -164,4 +164,4 @@ NOTE: Operators can restrict which node-selector label keys
CR authors are permi
The `builder.tasks` trait option lets CR authors inject arbitrary containers
into the build pipeline (only when using the `pod` build strategy). Each task
entry has the format `<name>;<image>;<command>[;<userID>]`.
-NOTE: Operators can disable custom task injection entirely by setting
`BUILDER_TASKS_ENABLED=false` on the operator deployment. When disabled, any
`builder.tasks` values provided by CR authors are silently ignored and an info
message is logged. The default is `true` (tasks are allowed). See
xref:installation:builds.adoc#env-var-config[build environment variables] for
details.
+NOTE: Operators can disable custom task injection entirely by setting
`BUILDER_TASKS_ENABLED=false` on the operator deployment. When disabled, any
`builder.tasks` values provided by CR authors are silently ignored and an info
message is logged. The default is `true` (tasks are allowed). See build
environment variables documentation for details.
