Adding info for conditions for autodiscovery (#921) (#936)

* Adding info for conditions

* Update docs/en/ingest-management/elastic-agent/configuration/autodiscovery/kubernetes-conditions-autodiscover.asciidoc

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>

* Update docs/en/ingest-management/elastic-agent/configuration/autodiscovery/kubernetes-conditions-autodiscover.asciidoc

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>

* Update docs/en/ingest-management/elastic-agent/configuration/autodiscovery/kubernetes-conditions-autodiscover.asciidoc

Co-authored-by: Giuseppe Santoro <giuseppe.santoro@elastic.co>

---------

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Co-authored-by: Giuseppe Santoro <giuseppe.santoro@elastic.co>
(cherry picked from commit e78f808)

Co-authored-by: Andrew Gizas <andreas.gkizas@elastic.co>

Author: mergify[bot]

docs/en/ingest-management/elastic-agent/configuration/autodiscovery/kubernetes-conditions-autodiscover.asciidoc

@@ -1,7 +1,13 @@
 [[conditions-based-autodiscover]]
 = Conditions based autodiscover
 
-You can define autodiscover conditions in each input to allow {agent} to automatically identify Pods and start monitoring them using predefined integrations. Refer to <<elastic-agent-input-configuration>> to get an idea .
+You can define autodiscover conditions in each input to allow {agent} to automatically identify Pods and start monitoring them using predefined integrations. Refer to <<elastic-agent-input-configuration>> to get an idea.
+
+IMPORTANT: Condition definition is supported both in *{agent} managed by {fleet}* and in *standalone* scenarios.
+
+For more information about variables and conditions in input configurations, refer to <<dynamic-input-configuration>>.
+You can find available variables of autodiscovery in <<kubernetes-provider>>.
+
 
 == Example: Target Pods by label