[Fleet] Create default Fleet Server policy with fleet server package

[nchaulet]

Summary

Resolve #90628

This create a Default Fleet Server policy during the setup (open to better naming :)) with the Fleet server package installed.

The policy is also created in the .fleet-policies indice with the flag default_fleet_server:true

Open discussion

I am wondering if we should evolve our datastructure for Agent Policy it start to be weird with all is_default is_managed, is_default_fleet_server and if we should maybe have something like a property tags that define the special feature of a policy like this tags: ['default']

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[ruflin]

• Can we delay the discussion around tags to separate it from this PR?
• @mostlyjason You will enjoy the naming discussion around the default policy name ;-). Lets not block on it as I assume we can update it at any time but lets make sure we come to a conclusion quickly.

[nchaulet]

@elasticmachine merge upstream

[nchaulet]

Can we delay the discussion around tags to separate it from this PR?

Totally we should not change the data model right now, I am just suggesting we start to thing about it.

[skh]

Please add some instructions how to test this. When I run this, and open the Fleet UI to trigger the setup, no fleet-server policy is created, and I don't see Fleet Server in the list of installed packages. Maybe I shouldn't because it's hidden? What am I missing?

---

Edited to add: I was missing xpack.fleet.agents.fleetServerEnabled: true. Thanks for the test description in #90658 .

[skh]

This works as described. When xpack.fleet.agents.fleetServerEnabled is set to true, the fleet server package is installed during setup, and a default fleet server policy is created.

[nchaulet]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 3313452

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
fleet	366.6KB	367.2KB	+605.0B

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/development-plugin-saved-objects.html#_mappings

id	before	after	diff
ingest-agent-policies	12	13	+1

History

• 💚 Build #106777 succeeded 2b8cb40
• 💚 Build #106592 succeeded 2b8cb40
• 💛 Build #105762 was flaky d2a29de
• 💔 Build #105655 failed 564a723

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream