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

new FAQ documentation #2867

Open
chrislovecnm opened this issue Jul 5, 2017 · 8 comments
Open

new FAQ documentation #2867

chrislovecnm opened this issue Jul 5, 2017 · 8 comments
Labels
area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@chrislovecnm
Copy link
Contributor

chrislovecnm commented Jul 5, 2017

Write a new FAQ document. The next question is; what do we include. Here are some ideas:

  1. there is no cli option to do x, how do I do it?
  2. how do I use my own image?
  3. how do I shut down my cluster and restart it?
  4. how do I make a change to an ami before or after an install, use a hook.
  5. What options do I have with DNS?

What else are we missing?

cc: @justinsb @geojaz @kris-nova @DerekV @WillemMali @kenden and whoever wants to pipe in

@kenden
Copy link
Contributor

kenden commented Jul 13, 2017

How to enable custom metrics? (from #1467)

@fedenusy
Copy link

fedenusy commented Nov 15, 2017

Q: kops get cluster isn't working: "error reading state store". ehrmehgehd?
A: make sure you have the right env vars set for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. if you already ran aws configure, try unsetting those env vars

@fedenusy
Copy link

@chrislovecnm also asked me to note that there's a FAQ about MFA, but not sure what the issue is

@mikesplain
Copy link
Contributor

I feel like there's should probably be a generic "my cluster didn't come up" section, maybe a checklist of sorts? Many times they're resolved by increasing instance size, or checking to make sure aws console to make sure ASG was able to spin up instances (either due to lack of availability or quota). If that doesn't resolve the issue, maybe mention the pertinent logs on the masters. As Justin brought up at office hours last week, we should do this in verify at some point but I think there's value in FAQs too.

@chrislovecnm
Copy link
Contributor Author

Add a section about RBAC

kubeAPIServer:
    authorizationMode: Node,RBAC

How to migrate to RBAC, and how to configure

@chrislovecnm
Copy link
Contributor Author

@mikesplain instance sizes should be fixed with the CPU changes, @justinsb wants a t2.micro to work 😆 But I am not certain.

Yes the whole protokube / dns-controller DNS - Dogs and Cats sleeping together needs to be explained

Another topic ... WTH is nodeup

@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 Feb 14, 2018
@chrislovecnm
Copy link
Contributor Author

/lifecycle frozen
/remove-lifecycle stale

@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/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants