New unique logging meta-data into key Kubernetes logs

[hase1128]

Enhancement Description

• One-line enhancement description (can be used as a release note): This KEP proposes a method for adding new three unique logging meta-data into K8s component logs.
• Kubernetes Enhancement Proposal: Trace context propagation #2312
• Primary contact (assignee): @hase1128
• Responsible SIGs: sig-instrumentation
• Reviewers: @serathius
• Approver: @dashpole
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.20)
  • Beta release target (x.y)
  • Stable release target (x.y)

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

[hase1128]

/sig instrumentation
/milestone v1.20

[k8s-ci-robot]

@hase1128: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/sig instrumentation
/milestone v1.20

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.

[zhijianli88]

/cc

[fenggw-fnst]

/cc

[johnbelamaric]

/milestone v1.20

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @hase1128 !

Enhancements Lead here, do you still intend to target this for alpha in 1.20?

Thanks!
Kirsten

[hase1128]

@kikisdeliveryservice

I would like to aim for 1.20 if possible, but 1.21 may be appropriate in terms of time.