Skip to content

Commit dd6c754

Browse files
committed
Add a known issue for agentless integrations
1 parent 8dd8487 commit dd6c754

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

solutions/security/get-started/_snippets/agentless-integrations-faq.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,11 @@ On the **{{fleet}}** page, agents associated with agentless integrations have na
5555
3. From the **Actions** menu, select **Request diagnostics .zip**.
5656
4. Download and unzip the [diagnostics bundle](/troubleshoot/ingest/fleet/common-problems.md#trb-collect-agent-diagnostics). Refer to [Common problems with {{fleet}} and {{agent}}](/troubleshoot/ingest/fleet/common-problems.md) for more information.
5757

58+
::::{note}
59+
In {{ech}} deployments on {{stack}} versions 9.0.0-9.1.5, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. This can result in agentless agents having an `Unhealthy` status.
60+
61+
This issue is resolved in {{stack}} 9.1.6 and 9.2.0. In these versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified.
62+
::::
5863

5964
## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration]
6065

@@ -72,4 +77,4 @@ When you create a new agentless CSPM integration, a new agent policy appears wit
7277

7378
## Can agentless integrations use a specific range of static IP addresses for configuring allow and deny rules for traffic?
7479

75-
No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.
80+
No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.

0 commit comments

Comments
 (0)