Add metrics of kube_pod_status_ready_time and kube_pod_status_containers_ready_time redux

[ryanrolds]

This is a copy of #1837 with the merge conflict resolved. All credit should go to @liangyuanpeng. The text below is copied from the other PR.

What this PR does / why we need it:
Base PR #1482

Ref: Adds kube_pod_status_ready_time and kube_pod_status_containers_ready_time metrics to get the information provided by Pod Lifecycle's PodConditions array.

Maybe we should support param to open this feature or not, juse like feature-gates.

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
increases metrics number that Pod number * 2

Which issue(s) this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1465

Co-authored-by: Szymon Grzemski sz.grzemski@gmail.com
Signed-off-by: Lan Liang gcslyp@gmail.com

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: liangyuanpeng / name: Lan (f36b8e6)
• ✅ login: ryanrolds / name: Ryan Olds (c3c0862)

[k8s-ci-robot]

Welcome @ryanrolds!

It looks like this is your first PR to kubernetes/kube-state-metrics 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kube-state-metrics has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[dgrisonnet]

Holding in favor of #1837 for now.

/hold

[logicalhan]

/triage accepted
/assign @mrueg

[mrueg]

Two small requests, then we should be able to merge it.

[mrueg]

Will this require Label Keys identifying the container?
Similar to createPodContainerInfoFamilyGenerator

[ryanrolds]

Checking

[ryanrolds]

My understanding is it's not that a specific container is ready, but all the containers are ready. If we emitting a metric about the status of individual containers, I would add container id so it could be joined to kube_pod_container_info. Thoughts?

[mrueg]

Yes, you're right! I was thinking it's using something in .status.containerStatuses which would be per container. No need to change anything then. :)

  - lastProbeTime: null
    lastTransitionTime: "2022-11-18T18:50:53Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2022-11-18T18:50:53Z"
    status: "True"
    type: ContainersReady

[mrueg]

/hold cancel
/lgtm

Thanks @liangyuanpeng and @ryanrolds for your contribution here!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrueg, ryanrolds

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mrueg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[valorl]

Thanks for this. Very relevant to me currently. @mrueg may I ask whether this will make it to 2.8 ? And if yes, do you maybe have a rough idea when that could be published ? I'm not familiar with the release process here 😇