Open chrislovecnm opened 7 years ago
How to enable custom metrics? (from https://github.com/kubernetes/kops/issues/1467)
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
@chrislovecnm also asked me to note that there's a FAQ about MFA, but not sure what the issue is
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.
Add a section about RBAC
kubeAPIServer:
authorizationMode: Node,RBAC
How to migrate to RBAC, and how to configure
@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
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
/lifecycle frozen /remove-lifecycle stale
Write a new FAQ document. The next question is; what do we include. Here are some ideas:
hook
.What else are we missing?
cc: @justinsb @geojaz @kris-nova @DerekV @WillemMali @kenden and whoever wants to pipe in