search

kubernetes / kops

Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
https://kops.sigs.k8s.io/
Apache License 2.0
15.78k stars 4.64k forks source link

new FAQ documentation #2867

Open chrislovecnm opened 7 years ago

chrislovecnm commented 7 years ago

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 commented 7 years ago

How to enable custom metrics? (from https://github.com/kubernetes/kops/issues/1467)

fedenusy commented 6 years ago

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 commented 6 years ago

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

mikesplain commented 6 years ago

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 commented 6 years ago

Add a section about RBAC 

kubeAPIServer:
    authorizationMode: Node,RBAC

How to migrate to RBAC, and how to configure

chrislovecnm commented 6 years ago

@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 commented 6 years ago

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

chrislovecnm commented 6 years ago

/lifecycle frozen /remove-lifecycle stale