diff --git a/docs/modules/ROOT/pages/scaling/binding.adoc b/docs/modules/ROOT/pages/scaling/binding.adoc
index 4124afeb78..027e28e136 100644
--- a/docs/modules/ROOT/pages/scaling/binding.adoc
+++ b/docs/modules/ROOT/pages/scaling/binding.adoc
@@ -99,6 +99,8 @@ A Pipe can automatically scale based on its CPU utilization and custom metrics u
 
 For example, executing the following command creates an _autoscaler_ for the Pipe, with target CPU utilization set to 80%, and the number of replicas between 2 and 5:
 
+WARNING: the HPA can work when the Pipe replica field needs to be specified. You need to scale the Pipe via `kubectl scale pipe my-pipe --replicas 1` or edit the `.spec.replicas` field of your Pipe to 1. This is due to a link:https://github.com/kubernetes/kubernetes/issues/111781[Kubernetes behavior which does not allow an empty value on the resource to scale].
+
 [source,console]
 ----
 $ kubectl autoscale klb <kamelet_binding_name> --min=2 --max=5 --cpu-percent=80
diff --git a/docs/modules/ROOT/pages/scaling/integration.adoc b/docs/modules/ROOT/pages/scaling/integration.adoc
index a6cab7d891..9a745cd15b 100644
--- a/docs/modules/ROOT/pages/scaling/integration.adoc
+++ b/docs/modules/ROOT/pages/scaling/integration.adoc
@@ -115,6 +115,8 @@ spec:
         averageValue: 1k
 ----
 
+WARNING: the HPA can work when the Integration replica field needs to be specified. You need to scale the Integration via `kubectl scale it my-it --replicas 1` or edit the `.spec.replicas` field of your Integration to 1. This is due to a link:https://github.com/kubernetes/kubernetes/issues/111781[Kubernetes behavior which does not allow an empty value on the resource to scale].
+
 More information can be found in https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/[Horizontal Pod Autoscaler] from the Kubernetes documentation.
 
 NOTE: HPA can also be used with Knative, by installing the https://knative.dev/docs/install/install-extensions/#install-optional-serving-extensions[HPA autoscaling Serving extension].