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

Implement base interface for most Kubernetes objects #101

Closed
dlaidlaw opened this issue Oct 19, 2017 · 7 comments
Closed

Implement base interface for most Kubernetes objects #101

dlaidlaw opened this issue Oct 19, 2017 · 7 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@dlaidlaw
Copy link

Most of the Kubernetes objects have a set of fields in common:

  • kind
  • apiVersion
  • metadata
  • spec

The objects that support this really need to reflect that by implementing an interface and possibly extending a base class.
@lwander
Copy link
Contributor

lwander commented Oct 25, 2017

Looks like OpenAPI supports this but is flagged as experimental. @mbohlool knows much more about the spec & how it's generated for k8s - is this on your radar?

@brendandburns brendandburns mentioned this issue Oct 26, 2017
Closed
@brendandburns
Copy link
Contributor

This has to happen via Swagger, I added this:

kubernetes/apiserver#23

To track.

@brendandburns brendandburns mentioned this issue Mar 22, 2018
Closed
@vibhupratap
Copy link

Was any work done on this. This will be very useful

@davidxia davidxia mentioned this issue Mar 18, 2019
Open
@russgold
Copy link
Contributor

russgold commented Apr 3, 2019

The Swagger issue keeps getting marked as 'stale'.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 2, 2019
@yue9944882
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 3, 2019
@brendandburns
Copy link
Contributor

Closing this since we now have this support with KubernetesObject and KubernetesListObject

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@dlaidlaw @russgold @lwander @brendandburns @yue9944882 @vibhupratap @k8s-ci-robot @fejta-bot