[Meta] Kubernetes package/integration

[ChrsMark]

This is a meta issue to keep track of the open issues we have regarding the Kubernetes package/integration.

Open issues

• Deployment strategy for Standalone and Managed version of Agent: [Elastic Agent] [Meta] Gathering logs and metrics from Kubernetes without using fleet generated agent config and without central agent management via fleet beats#23613
• Refactor kubernetes metricsets to use single calls per endpoint to improve performance. For instance, state_* metricsets fetch the same amount of data to only store some of them according the target k8s object. This can be improved if metricsets can share the input. Some goes for pod, node, volume, container and system metricsets that get the same input from Kubelet's api -> Refactor kubernetes metricsets to use single calls per endpoint beats#24869
• We want the Kubernetes integration to look like AWS, with one package shipping multiple integrations: kubelet, kube_state, etc.. Outcome from [AWS] Add support for granular search of cloud service integrations #526 should be able to apply to kubernetes integration as well -> https://github.com/elastic/beats/issues/24870
• Integration tests: Add integrations tests for k8s package #822
• ECS (Common fields for Orchestrators #442, Verify ECS alignment in container fields reported by kubernetes module and meta processor beats#23585)

[ChrsMark]

@masci feel free to comment/edit/add on the description

[andresrc]

Thanks @ChrsMark !!

[ruflin]

@ChrsMark If my understanding is correct, point 1,3,4 are a requirement, 2 is an improvement.

[ChrsMark]

@ChrsMark If my understanding is correct, point 1,3,4 are a requirement, 2 is an improvement.

@ruflin that's correct