Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Umbrella documentation issue #90

Closed
12 of 19 tasks
pieterlange opened this issue Nov 23, 2016 · 6 comments
Closed
12 of 19 tasks

Umbrella documentation issue #90

pieterlange opened this issue Nov 23, 2016 · 6 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@pieterlange
Copy link
Contributor

pieterlange commented Nov 23, 2016

There's a bit of documentation already out there, but some of it is hard to find and a lot of it is outdated. The move to the dedicated repo included a bunch of improvements of which nearly all are mostly documented in github issues.

Proposal for documentation checklist:

@mumoshu
Copy link
Contributor

mumoshu commented Nov 24, 2016

Thanks for starting this!

@mumoshu mumoshu added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Dec 1, 2016
@aholbreich
Copy link

Anyone likes the idea of something like GOALS.md which I've mentioned in #59 (comment)?

yes, me ;)

@mumoshu
Copy link
Contributor

mumoshu commented Dec 10, 2016

Added "Fixes", "Currently un-documented pre-requisites", "Custom configuration" to the list.

@mumoshu
Copy link
Contributor

mumoshu commented Jan 13, 2017

@aholbreich FYI, regarding one of your comment:

Allows management of several clusters in convenient way

Probably in a way other than you might have expected but the work is ongoing at #238.

frickjack added a commit to uc-cdis/cloud-automation that referenced this issue Dec 13, 2017
provisioner permissions are still too broad -
kube-aws has an open issue to more clearly specify
the permissions needed for kube-aws:
    kubernetes-retired/kube-aws#90
@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 the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2019
@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

@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 May 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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

5 participants