Elastic Agent with Private Service connect

[Chris_Pinto]

Hi Team,

Is there a way to add multiple fleet hosts endpoint in the fleet and create a separation based on the agent policies?

Our current Elastic deployment hosted on Elastic cloud has default fleet hosts and the agents are enrolled to the fleet and working as expected.

We have a new requirement to install elastic agent on Google environment and setup private communications between GCP and Elastic cloud using private service connect - GCP Private Service Connect traffic filters | Elasticsearch Service Documentation | Elastic

The problem with this setup is that, we need to add a new fleet host to the fleet - https://<Fleet cluster ID/deployment alias>.fleet.:443. When we add the fleet host, the existing agents enrolled with the default fleet host goes into unhealthy state because the agents try to connect to the new PSC host URL. The agents go into a unhealthy state because the DNS for the fleet host is hosted in the GCP private zone and existing agents are unaware of this domain.

Here is the error message from the existing Elastic agent
[elastic_agent][error] failed to dispatch actions, error: fail to communicate with updated API client hosts: Get "https://<Fleet cluster ID>.fleet.<private zone DNS name>:443/api/status?": lookup <Fleet cluster ID>.fleet.<private zone DNS name: Temporary failure in name resolution

[Cristina_Amico]

Hi @Chris_Pinto,

Regarding your first question, it's not currently possible to add multiple fleet hosts and tie the agent policies to them, but this feature is coming in 8.6.0. So, if you have the requirement to have separate fleet server hosts per policy, I recommend you update to 8.6.0 as soon as it comes out.

Regarding the error, is this happening only on existing agents or also on the new ones?

[Chris_Pinto]

Thank you, Cristina.

The error is happening on the existing agents and the only possible solution I think here is to tie the agent policy to the required fleet hosts. That way, the existing agents does not try to establish a connection with the PSC Fleet host.