4 ms·
Technically speaking: cool Practically speaking: I worry this will become a parallel but subtlety different implementation of Kubernetes with it's own quirks.
by meddlepal 8y ago
Technically speaking: cool
Practically speaking: I worry this will become a parallel but subtlety different implementation of Kubernetes with it's own quirks.
- dankohn1 8y agoThat's why CNCF is thrilled that Rancher passed our Certified Kubernetes conformance tests for k3s prior to the public announcement. https://landscape.cncf.io/category=certified-kubernetes-distribution,certified-kubernetes-hosted,certified-kubernetes-installer&format=card-mode&grouping=category&selected=k3s https://landscape.cncf.io/category=certified-kubernetes-dist...
- meddlepal 8y agoAh, interesting! Cool. Thanks.
- nvarsj 8y ago> Practically speaking: I worry this will become a parallel but subtlety different implementation of Kubernetes with it's own quirks. Hello, we're already there. Despite the CNCF certification process, there are many flavours of k8s, all with their own quirks. Being on the product side, it is quite painful to support.
- meddlepal 8y agoI am aware of this problem (getambassador.io dev as well as infra engineer). The differences usually manifest at the edges rather than the internals right now. This has the potential to be even more disruptive problem. I agree the CNCF certification process isn't comprehensive enough.
- nvarsj 8y agoWell, even the internals have issues. Take Openshift as the most extreme example - it's a fork of K8s, with a lot of custom functionality like scc and routes, and also a lot of custom behavior like its admission controllers that manage pod security contexts. It's almost like a different version of k8s - things that will run on GKE or vanilla k8s won't work on Openshift. Yet, it is CNCF compliant.