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 enough information to resolve object references and label selectors generically #38216

Open
bgrant0607 opened this issue Dec 6, 2016 · 10 comments
Open

Expose enough information to resolve object references and label selectors generically #38216

bgrant0607 opened this issue Dec 6, 2016 · 10 comments
Labels
area/app-lifecycle area/extensibility lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@bgrant0607
Copy link
Member

The API has a number of references to other resources that don't specify full details needed to construct API calls (e.g., secretName) without specific, detailed knowledge of the API. Clients need to be able to resolve dependencies generically.

There are a few possible approaches. One could be to augment the OpenAPI spec. Another could be to provide a subresource or alternative representation (#33900) to enumerate fully qualified dependencies.

See also #3676.
@bgrant0607 bgrant0607 added area/app-lifecycle area/extensibility sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Dec 6, 2016
@0xmichalis
Copy link
Contributor

@kubernetes/sig-api-machinery

@caesarxuchao
Copy link
Member

Are there more context/use cases for the problem?

@deads2k
Copy link
Contributor

deads2k commented Dec 7, 2016

Are there more context/use cases for the problem?

Off the top of my head

  1. rolebindings have a roleref
  2. secretvolumesources have a secret ref
  3. configmapvolumesources have a configmap ref which uses a local ref (which I was prevented from adding group and kind to when I made it).
  4. clusterspecs have a secret reference
  5. glusterfsvolumesources have an endpoints reference
  6. RBDvolumesources have a secret ref
  7. podspecs refer to service accounts
  8. serviceaccounts reference secrets in two different ways
  9. the entire ownerref object is a logical reference
  10. HPAs have a reference to what they need to scale

@bgrant0607 bgrant0607 mentioned this issue Mar 29, 2017
Open
@fejta-bot
Copy link

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@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 Dec 19, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 18, 2018
@bgrant0607
Copy link
Member Author

/remove-lifecycle rotten
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jan 18, 2018
@pranav-pandey0804
Copy link

hi @bgrant0607 ,
it's been a while since any updates on this issue, Is there any progress or update on the approaches previously discussed, such as augmenting the OpenAPI spec or providing alternative representations?

@pranav-pandey0804
Copy link

if there has been limited progress, I would be interested in collaborating on a proposal or prototype. Specifically, enhancing the OpenAPI specification seems like a promising approach that could benefit a wide range of users!

@pranav-pandey0804
Copy link

Could we consider setting up a working session to discuss this further, or is there an upcoming SIG meeting where this could be addressed?

@pranav-pandey0804
Copy link

Additionally, if there are particular areas within the proposed enhancements that need more hands-on testing or development, I am ready to contribute. Please let me know how I can help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/app-lifecycle area/extensibility lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@caesarxuchao @0xmichalis @bgrant0607 @deads2k @k8s-ci-robot @fejta-bot @pranav-pandey0804