diff options
| author | Everton Seiei Arakaki <30481051+EvertonSA@users.noreply.github.com> | 2023-04-19 00:23:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-19 00:23:01 +0200 |
| commit | 6a7cdf42dcbab3fe9cacb5b98cce79d0e034d57d (patch) | |
| tree | 39008b1943685a3bd72fc09a23e36feaa50280d5 | |
| parent | 22177b7aafcc36503c44642d450206e906d6a388 (diff) | |
docs: detail impressions
| -rw-r--r-- | ADOPTERS.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ADOPTERS.md b/ADOPTERS.md index 63473e0..4ef7aec 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -4,4 +4,4 @@ This is a list of adopters of Robusta KRR operator: Everton Arakaki - WAES Platform Consultant for Semiconductor Industry
-> I used Robusta KRR in my production clusters, and it took me less than 5 minutes to get very "robust" recommendations. Our applications and platform tooling were discovered automatically; our kubecontext was discovered automatically; and our kube-prometheus-stack was discovered automatically. It's just a matter of having Python and you are ready to use KRR. I'm eager to implement KRR recommendations in production, and try once again. I will come back here with more feedback.
\ No newline at end of file +> I used Robusta KRR in my production clusters, and it took me less than 5 minutes to get very well detailed cpu/memory recommendations. Our applications and platform tooling were discovered automatically; our kubecontext was discovered automatically; and our kube-prometheus-stack was discovered automatically. It's just a matter of having Python and you are ready to use KRR. I'm eager to implement KRR recommendations in production, and try once again. I will come back here with more feedback.
\ No newline at end of file |