I am also using EKS and wanted to know if yet they have solved this or is there a way around without using kops. Unable to comment on the same question because of low credits, hence posting this as a new question.
Asked
Active
Viewed 111 times
2
-
maybe you should comment to the other question if you want to see if there was an update? – Jonathan Jul 30 '18 at 07:43
-
Minimum credits required to comment is not satisfied, hence the new question – Ankur garg Jul 30 '18 at 07:44
-
Sorry forgot about this one. Can you alter the question with this info, so I can undo the downvote? – Jonathan Jul 30 '18 at 07:55
-
I have made the required edit – Ankur garg Jul 30 '18 at 08:06
-
Check this out as a workaround until amazon fixes eks https://medium.com/eks-hpa-workaround/k8s-hpa-controller-6ac2dfb4c028 – James Smith Aug 17 '18 at 19:15
1 Answers
0
Kops is better suited than EKS since there is no way to configure kube config in EKS for the horizontal pod autoscalar default time and even the metric collection does not work by default. I used both of them and it looks like EKS does not provide any additional value over kops for aws.
Ankur garg
- 21
- 4