Update index.md

content/cost_optimization/index.md

@@ -18,3 +18,9 @@ There are three general best practice areas for cost optimization in the cloud:
 + Optimizing over time (Right Sizing)
 
 As with the other best practices, there are trade-offs to consider. For example, do you want to optimize for speed to market or for cost? In some cases, it’s best to optimize for speed—going to market quickly, shipping new features, or simply meeting a deadline—rather than investing in upfront cost optimization. Design decisions are sometimes guided by haste as opposed to empirical data, as the temptation always exists to overcompensate “just in case” rather than spend time benchmarking for the most cost-optimal deployment. This often leads to drastically over-provisioned and under-optimized deployments. 
+
+
+This guide includes a set of recommendations that you can use to improve the cost optimization of your Amazon EKS cluster.
+
+## Feedback
+This guide is being released on GitHub so as to collect direct feedback and suggestions from the broader EKS/Kubernetes community. If you have a best practice that you feel we ought to include in the guide, please file an issue or submit a PR in the GitHub repository. Our intention is to update the guide periodically as new features are added to the service or when a new best practice evolves.