4 ms·
I don't think being 3 months behind upstream release cycle is 'dragging their feet', but more 'waiting for stabilization' and 'researching and implementing requ
by mattashii 6y ago
I don't think being 3 months behind upstream release cycle is 'dragging their feet', but more 'waiting for stabilization' and 'researching and implementing required changes'.
- csunbird 6y agoThey started supporting 1.17 very recently, I think, because last time I checked when 1.17 was the latest stable kubernetes version, they were supporting 1.14 only. EKS is usually behind. Edit: I stand corrected. 1.17 was officially supported on July, 1.16 on April and 1.15 on March. Those versions were released a long time ago.
- mattashii 6y agoTrue, on 17 July EKS announced k8s 1.17 GA, 1 May was k8s 1.16 GA, and 10 March for 1.15. They've been catching up. But, being behind is expected from a SaaS offering of 3rd party software: it takes time to ensure you can deliver the quality of service your customers expect, and for 3rd party software you don't get a head start.