Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We were looking rather favourably at CoreOS as an enterprise friendly, yet lightweight alternative to OS. LDAP/RBAC/Prometheus are the type of features that we are looking for, on the other hand we have our own build tooling and release process, hence no use for that part of Openshift. I find it hard to recommend using a K8S distribution that has so many batteries included, 75% of which my organization doesn't need or use. Sorry to see Tectonic go.


Being from CoreOS, I understand your sentiment. Part of our long term integration goal with OpenShift is to try and package up all of its components as Operators that can be optionally installed with our Operator Lifecycle Manager[0]. This is the software that powered Tectonic's Open Cloud Services. In addition, we're rolling out an installer based on the Tectonic installer. The end result should be an installation process similar to Tectonic and Kubernetes cluster running very few services, until you decide to install additional Operators for the functionality you want.

[0]: https://github.com/operator-framework/operator-lifecycle-man...


Good to hear. It’s been awesome to see this pattern go from idea to community best practice.


Thanks for your response, it is good to know that these things are being considered.


Agreed. Preferred the Tectonic approach and roadmap based on CoreOS founder Alex Polvi‘s mission to secure the Internet:

https://coreos.com/blog/why-we-started-coreos

When at my new gig we suggested RH should understand the sec and ops value of CoreOS thinking, we didn’t mean take them off the market. :-)

Alex, Brandon, still want what you were building.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: