add exitcode to labels of kube_pod_init_container_status_terminated_reason

[dafenko]

What would you like to be added:
Add exitcode to labels of kube_pod_init_container_status_terminated_reason

Why is this needed:
Our application has defined exit codes. We would like to be alerted when app ends up with a specified error code.

Describe the solution you'd like
We would like to define alert that uses kube_pod_init_container_status_terminated_reason metric and be alerted when container exists with certain exit code.

Additional context
We are using node.js. Node.js has limit for memory allocation. (see NODE_OPTIONS --max-old-space-size=)
We intentionally keep limit for node.js a few percent less then K8S resource limit.
In that way node.js has possibility to handle OOM (e.g. create dump file).
POD gets then signal SIGABRT 6 (exit code 128+6 = 134).
We would like to be alerted when such situation happens.

[slashpai]

I would like to work on this. I will review and update back

/assign

[dannylee-]

Would it be better to create a new metric with the exit code? Or else we would introduce a label with a large cardinality (256 possible values)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[prashantv]

/reopen

Having exit code would be useful for monitoring different types of container exits.

[k8s-ci-robot]

@prashantv: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Having exit code would be useful for monitoring different types of container exits.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fgiannetti]

I would like to work on this. I will review and update back

/assign

Hey @slashpai
Have some news about this? It would be really useful to have this feature ;)
Or maybe this message will reopen this issue...
Thank you!!

[ssabo]

/reopen

[k8s-ci-robot]

@ssabo: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[anatoli-klamer]

/reopen

[k8s-ci-robot]

@anatoli-klamer: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.