ECK Fleet Server setup confusion and failure

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hi,

I have an existing ECK stack (ES + Kibana) running fine. I’m now trying to add Fleet Server and configure Kibana accordingly, but I’m a bit confused.

I’m following:

Am I right to assume that the xpack.fleet.packages / xpack.fleet.* section in the Kibana CR is responsible for creating the Fleet Server agent policy (e.g. eck-fleet-server)?

My Fleet Server logs show:

failed to request /api/fleet/enrollment_api_keys (404)

Agent policy "eck-fleet-server" not found

So it looks like the policy is missing, or a problem of authentication maybe ?

Thanks!

2

Unfortunately I think you may hit Kibana issue [Fleet] Preconfiguration API doesn't support updating / adding / removing package_policies · Issue #111401 · elastic/kibana · GitHub .

This bug is also described in [Fleet] Improve preconfiguration ergonomics · Issue #190333 · elastic/kibana · GitHub