KEP-4753: Expose `ownerReferences` via `valueFrom` and downward API

[ArangoGutierrez]

Enhancement Description

• One-line enhancement description: Expose ownerReference via valueFrom and downward API to prevent pods from calling the API server to retrieve said information.
• Kubernetes Enhancement Proposal: <TBD>
• Discussion Link:
  • Issue at https://github.com/kubernetes/kubernetes/issues/116662
• Primary contact (assignee):
  • @ArangoGutierrez
• Responsible SIGs:
  • /sig node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.31):
  • Beta release target (1.32):
  • Stable release target (1.33):
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4754
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

[ArangoGutierrez]

/sig node

[kannon92]

Hey! @ArangoGutierrez are you planning on working on this during the 1.32 cycle?

[haircommander]

according to https://github.com/kubernetes/enhancements/pull/4754#issuecomment-2399356095 this is being worked on. No guarantees we'll be able to find approver bandwidth, but for the sake of consistent paperwork

/milestone v1.32 /label lead-opted-in

I would consider this at risk of missing freeze, but it's worth a try

[shecodesmagic]

Hello @ArangoGutierrez 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable for latest-milestone: v1.32.
• [ ] KEP readme has up-to-date graduation criteria
• [ ] KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would need to update the following:

• [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable for latest-milestone: v1.32.
• [ ] KEP readme has up-to-date graduation criteria
• [ ] KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP. The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!