-
Notifications
You must be signed in to change notification settings - Fork 47
Update docs #208
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
Update docs #208
Conversation
README.md
Outdated
| * [Operator](operator/README.md) | ||
| * [KIT-environment](substrate/README.md) | ||
| * [TestBed](testbed/README.md) | ||
| The EKS Scalability team is responsible for improving performance across the Kubernetes stack. We started our journey by manually running tests against modified EKS dev clusters. This helped us to identify some bottlenecks, but results were difficult to demonstrate and reproduce. We wanted to increase the velocity of our discoveries, as well as our confidence in our results. We set out to build automation to help us configure cluster components, execute well known test workloads, and analyze the results. This evolved into KIT, and we’re ready to share it to help accelerate testing in other teams. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if we should provide this section in the public repo, or we might want to consider removing the section talking about the difficulty of testing on EKS dev clusters.
docs/how-to-use-kit.md
Outdated
|
|
||
| ### Use-cases supported with KIT | ||
|
|
||
| * As a Kubernetes developer/user, create x number of objects(pods, secrets, config maps) in a cluster. As part of the validation, I want to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this section be a little more concise? For example I don't think we need to prefix each bullet with "As a Kubernetes developer/user."
|
|
||
| ## Key Terms | ||
|
|
||
| **KIT/clusters or guest clusters -** These are rapid prototyping vanilla Kubernetes clusters provisioned using using EKS-distro images. They take about 3-4 minutes to provision on ec2 nodes and less than 30 seconds to update their configurations. These clusters are provisioned by KIT-operator running in the KIT environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: should this be "KIT clusters or guest clusters"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have been using these interchangeably, so want to make sure both are covered.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 41 references quip which is AWS internal only ;)
Issue #, if available:
#100
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.