Enhancements: 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: #1961
• 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.

[kikisdeliveryservice]

Hi @hase1128

We will track for now and you can just keep us updated.

[kikisdeliveryservice]

As a note I left some comments on your KEP PR that will need to be resolved as well: https://github.com/kubernetes/enhancements/pull/1961#pullrequestreview-489905153

[ehashman]

Assuming the KEP is completed and approved, we will target 1.20; otherwise this will slip to 1.21 for alpha.

[kikisdeliveryservice]

Assuming the KEP is completed and approved, we will target 1.20; otherwise this will slip to 1.21 for alpha.

Great. We are tracking it for now, let us know if anything changes. As a note Enhancements Freeze is October 6th and the KEP will need to be merged, implementable (it's currently provisional) as well as have test plans and graduation criteria added. Would also be good to fill out the PRR.

[kinarashah]

Hi @hase1128,

Enhancement shadow for 1.20 release here 👋. As we're moving close to the Enhancement Freeze deadline (October 6), just wanted to remind you to update KEP PR.

We're looking for the KEP PR to have the following before this deadline:

• should have test plans
• should have graduation criteria
• should have state implementable and merged

Please let me know if you have any questions, thank you!

[kikisdeliveryservice]

@ehashman @hase1128 :

Has this slipped to 1.21? the kep update seems to say so: https://github.com/kubernetes/enhancements/pull/1961/files#diff-168484bdbc7e288639cb3b3a8cfc7552

[hase1128]

I think it will be 1.21.

[kikisdeliveryservice]

I think it will be 1.21.

Thanks for the update!

/milestone clear

[ehashman]

Ack from SIG Instrumentation leads/regular meeting on pushing to 1.21.