Hacker News Reader

Comment by candiddevmike | Hacker News Reader

It's getting harder and harder to find the kubernetes part of openshift--wtf is openshift-dns? I'm not sold that this is better than k3s, and I think red hat isn't capable of balancing the needs of both a sprawling borg-like platform that assimilates all kube functions vs a lean kube experience.

View on HN

> wtf is openshift-dns

I think one thing I'm definitely missing from the OpenShift docs [1] is reasoning. What does it add? Why do I want to learn to use an operator instead? Otherwise, it's pretty clear that it's just an operator on top of CoreDNS.

I do think that the docs are utterly devoid of Kubernetes content. I think historically, RH tried to differentiate themselves from K8s. Now, it can definitely hurt the knowledge migration and transfer.

[1] https://docs.openshift.com/container-platform/4.8/networking...

I can't speak for Red Hat but I have a lot of experience with OpenShift.

Basically all of these operators are there to allow customization. The philosophy behind OpenShift is to move everything possible to operators so they can be managed in a cloud native way. This has a bunch of benefits like being fully declarative, and able to keep your whole config in version control.

Red Hat is definitely not going for a "lean" kube experience. OpenShift is heavy AF (for good reasons but still). They're going for "this includes everything you need for a full platform." For users that are openshift on the backend it's pretty nice to have uniformity with the edge too. This will be "light enough" for most cases although of course it can be further improved.

Openshift-dns is just their custom operator which deploys and configures CoreDNS. OpenShift is k8s with alot of RH operators bundled in to configure stuff like monitoring, logging, networking, ingress, etc.

Reply on news.ycombinator.com