Re:Is K8s Too Complicated? 
by Filligree on Saturday May 12, 2018 @12:03PM
(#17054672)
You mean, it's stable. That sounds like a good reason to use it, not to avoid it.
[ Parent
| on HN ]
Re:Is K8s Too Complicated? 
by ad_hominem on Saturday May 12, 2018 @01:22PM
(#17055026)
Not really; I had an issue that silently broke renewals. When I found the open issue that corresponded to it the maintainers were herding people to cert-manager. There are a lot of issues where they are doing that (besides very obviously at the top of the README with warning symbols).
At the very least it's eventually going to break on newer versions of Kubernetes. Maintenance-only != LTS.
Maintenance-only usually means deprecated. There are some areas in the software world where maintenance-only can last a long time and can be de facto LTS. The Kubernetes ecosystem is not one of them.
It doesn’t support ACMEv2, Wildcard certs, and more. And Certmanager is alpha. The alternatives are all horrible.
From the Kube-lego github page, it looks like the last version of k8s is supports is 1.8, which will only be supported until 1.11 comes out.
So sounds more like it's deprecated than stable.
Depends on where you come from. In JS world, stable means there's a fork in it, and it's grayer than last weeks' meat. In server-side world, that means you're good to build a business on it for 15 years