[Epic] Selective monitoring of workloads through user provided conditions on fleet UI

[mlunadia]

Context

Picking up context from elastic/beats#23876
We want to enable users to monitor Kubernetes workloads through user-provided conditions on the fleet UI

Problem definition

Elastic operators need to collect and ingest data from workloads that have a characteristic that is not necessarily aligned with the Kubernetes infrastructure.

User outcome

Elastic operators can define the conditions that a workload which is to be monitored needs to meet in order for it to be observed. Workloads that meet the conditions defined by the Elastic Operator will have a frictionless experience that will not require further steps from the user side.

Solution hypothesis

We believe that providing Elastic operators with a conditions field in the fleet UI will enable them to decide which workloads need to be monitored

Dependency on Fleet UI

Kibana issue: elastic/kibana#108525

[gizas]

elastic/integrations#1867 relevant issue

[ChrsMark]

Actually elastic/integrations#1867 is describing exactly the same. I will go ahead and close it in honor of this one.

This specific one would be covered by elastic/elastic-package#949 (comment).

Also for reference, this one is not about "hint's based autodiscovery", so not related to elastic/beats#23876 as mentioned in the issue description. This one is about static/template/condition based autodiscovery which the equivalent of what is described for Beats at https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-autodiscover.html#_kubernetes.

Kibana issue: elastic/kibana#108525

cc: @gizas @mlunadia