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.

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

System Correctness: Single Source for Default Values #55

Closed
1 task done
aronchick opened this issue Jul 22, 2016 · 9 comments
Closed
1 task done

System Correctness: Single Source for Default Values #55

aronchick opened this issue Jul 22, 2016 · 9 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/ui Categorizes an issue or PR as relevant to SIG UI.
Milestone

Comments

@aronchick
Copy link
Contributor

aronchick commented Jul 22, 2016

Description

Developers have a single place where defaults should be coded, and kubectl doesn't need to roundtrip json before sending it to the apiserver

kubectl doesn't apply defaults or overwrite apiserver - the apiserver is the single place where defaults are intelligently created. cc @lavalamp

@aronchick aronchick added this to the v1.4 milestone Jul 22, 2016
@idvoretskyi
Copy link
Member

idvoretskyi commented Jul 25, 2016

cc @kubernetes/kube-ui-maintainers

@idvoretskyi idvoretskyi added the sig/ui Categorizes an issue or PR as relevant to SIG UI. label Jul 25, 2016
@lavalamp lavalamp assigned krousey and unassigned lavalamp Aug 25, 2016
@lavalamp
Copy link
Member

This is in and done, but most of these boxes don't make any sense for this feature. And @krousey doesn't seem to have permissions to check them, anyway.

@lavalamp
Copy link
Member

I edited the OP and deleted boxes that don't make much sense for this feature.

@idvoretskyi
Copy link
Member

@lavalamp any documentation is going to be provided for this feature?

@lavalamp
Copy link
Member

This doesn't really need documentation IMO and doesn't even belong in the features repo

@lavalamp
Copy link
Member

Unless @krousey feels differently.

@philips
Copy link
Contributor

philips commented Sep 21, 2016

Agreed. I think this should be closed. @aronchick ?

@aronchick
Copy link
Contributor Author

Agreed
On Wed, Sep 21, 2016 at 14:53 Brandon Philips [email protected]
wrote:

Agreed. I think this should be closed. @aronchick
https://github.com/aronchick ?


You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#55 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADIdSQqOW7TqBxXc7wVcx2RxJbt8nxpks5qsadhgaJpZM4JTI6A
.

@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.

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 Jan 2, 2018
@lavalamp lavalamp closed this as completed Jan 2, 2018
ingvagabund pushed a commit to ingvagabund/enhancements that referenced this issue Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/ui Categorizes an issue or PR as relevant to SIG UI.
Projects
None yet
Development

No branches or pull requests

8 participants