Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose ownerReferences via valueFrom and downward API #116662

Open
thockin opened this issue Mar 15, 2023 · 8 comments
Open

Expose ownerReferences via valueFrom and downward API #116662

thockin opened this issue Mar 15, 2023 · 8 comments
Assignees
@ArangoGutierrez @ArkaSaha30
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@thockin
Copy link
Member

thockin commented Mar 15, 2023

There are cases where it's useful for a pod to know its own owner.

This would need a KEP to argue the formatting and edge cases, but shouldn't be too hard.

xref gocrane/crane#716
@thockin thockin added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. labels Mar 15, 2023
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 15, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@thockin thockin mentioned this issue Mar 15, 2023
Open
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2023
@thockin thockin removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2023
@ArkaSaha30
Copy link
Member

Hello @thockin 👋 , I am interested to work on this issue and start with the KEP.
/assign

@ArkaSaha30
Copy link
Member

Hi @thockin, I have went through the gocrane/crane#716 discussion and as far as I can understand the ask is to expose ownerReferences as a part of env or downwardAPI similar to what we do with metadata.name.
Please confirm if I have understood the issue correctly and also a bit more details as to how to start working on it.

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 24, 2024
@thockin thockin added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 1, 2024
@ArangoGutierrez
Copy link
Contributor

This will help us to fix kubernetes-sigs/node-feature-discovery#1752
I am happy to take on this @thockin
/assign

@ArangoGutierrez
Copy link
Contributor

Do we still need the needs-triage @thockin ?

@thockin thockin added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 4, 2024
@ArangoGutierrez ArangoGutierrez mentioned this issue Jul 8, 2024
Open
4 tasks
@ArangoGutierrez
Copy link
Contributor

KEP process started kubernetes/enhancements#4753

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ArangoGutierrez ArangoGutierrez

@ArkaSaha30 ArkaSaha30

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@thockin @ArangoGutierrez @k8s-ci-robot @ArkaSaha30 @k8s-triage-robot