Add pod.status_reason and pod.status.ready_time fields state_pod data stream

[MichaelKatsoulis]

Proposed commit message

• WHAT: Enhance kubernetes state_pod metricset with kubernetes.pod.status_reason and kubernetes.pod.status.ready_time fields.
• WHY: Useful new metrics that indicate the reason a pod might not be in a desired state and the time it took for a pod to become ready.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

How to test this PR locally

1. create local k8s cluster: kind create cluster
2. install stack: elastic-package-0.98.2 stack up -d -v --version=8.15.0-SNAPSHOT
3. Install kubernetes integration version 1.63.0 and assign it to policy and a managed agent
4. Create a pod with a low resources.limits.memory to cause OOMKilled

Related issues

• Relates Collect kube_pod_status_ready_time from KSM for kubernetes.state_pod metriscet beats#39158
• Relates Kubernetes integration: add pod status reason #9752

Screenshots

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: cc3056a

History

• 💔 Build #13397 failed 70398f5
• 💔 Build #13361 failed 64ce880
• 💚 Build #13353 succeeded e85b0c8

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
66.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

Package kubernetes - 1.63.0 containing this change is available at https://epr.elastic.co/search?package=kubernetes