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

StatefulSet 1.5 umbrella #1655

Closed
erictune opened this issue Nov 9, 2016 · 9 comments
Closed

StatefulSet 1.5 umbrella #1655

erictune opened this issue Nov 9, 2016 · 9 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone

Comments

@erictune
Copy link
Member

erictune commented Nov 9, 2016

I've written a detailed docs plan for StatefulSet for 1.5. There is a lot to do between now and the Docs freeze.

It was too dynamic to use a github issue or markdown. I used a Google doc:

https://docs.google.com/document/d/1F5UHlYLDmS2V-J4xPDwFiLAujOk-kt03qKK3Wgthsnc/edit#

I made it world viewable and commentable for anyone in Sig-Apps which should cover most interested people, but DM me (erictune) on slack if you need an invite or whatever.

If you are interested in helping identify missing topic or writing docs, take a look. Warning: it is a long doc.

@erictune erictune added this to the 1.5 milestone Nov 9, 2016
@chrislovecnm
Copy link
Contributor

When is the date for doc freeze? Will review when I can

@enisoc
Copy link
Member

enisoc commented Nov 10, 2016

@jimmycuadra
Copy link
Contributor

Eric, will you make the "rename plan" linked from that Google Doc world readable, please? Thanks for putting this together!

@enisoc
Copy link
Member

enisoc commented Nov 10, 2016

I've changed the link to point to the published version: kubernetes/kubernetes#35534

@bluecmd
Copy link

bluecmd commented Dec 21, 2016

FWIW, http://kubernetes.io/docs/api-reference/apps/v1beta1/definitions/ is not linked into the navigation tree (reports "Support").

@enisoc
Copy link
Member

enisoc commented Dec 21, 2016

@bluecmd Thanks for reporting. I think I found where someone is trying to fix it, although the PR appears to be stuck: #1947

@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 5, 2018
@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 Feb 9, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

8 participants