51–60 of 76 posts
Earlier quoted context omitted.
You're also welcome to look at the kubernetes stats here: https://cncf.biterg.io You can clearly see the diverse number of contributors/companies
Cauldron[1] looks awesome! Are you on the team / can you get me an invite code? [1] https://cauldron.io/
Please, have in mind it is (for now) just a proof of concept.
I hope they make it easier too. Theres no documentation what so ever for installing kubernetes on coreOs yet they endorse using coreOs
The CoreOS site maintains guides for various options: https://coreos.com/kubernetes/docs/latest/ I would love your feedback on the mailing lists or twitter: https://coreso.com/community
Pardon me if this is somewhere right under my nose, but what is it that Heptio will actually do to "Bring Containers to Enterprise"? Will they maintain a commercial Kubernetes spin, ala Tectonic? Are they going to be mostly about consulting? Will they sell any add-ons?
[disclosure: Craig -- CEO] to name a few 1. support and services. this is a really important factor for most enterprises; they want to know they have expert staff on call who have a decent shot at getting a change they need upstreamed. 2. consolidation and operations at scale. turns out Kubernetes is being deployed as a 'devops tool' today and people create lots of teensy clusters. we built it to be super flexible an…
Pardon me if this is somewhere right under my nose, but what is it that Heptio will actually do to "Bring Containers to Enterprise"? Will they maintain a commercial Kubernetes spin, ala Tectonic? Are they going to be mostly about consulting? Will they sell any add-ons?
[disclosure: Craig -- CEO] to name a few 1. support and services. this is a really important factor for most enterprises; they want to know they have expert staff on call who have a decent shot at getting a change they need upstreamed. 2. consolidation and operations at scale. turns out Kubernetes is being deployed as a 'devops tool' today and people create lots of teensy clusters. we built it to be super flexible an…
And it begins. The birth of a company with a direct conflict of interest in making Kubernetes so simple to use/administer that you don't need to pay another company for 'enterprise support'. This happens quite frequently with open source infrastructure. Keep an eye on them to push back against improvements that directly conflict with their company's "enterprise sauce".
Earlier quoted context omitted.
Like OpenStack?
OpenStack has begun to feel more of a vendor marketplace with each of them trying to see if you can adopt their flavor. It looks somewhat similar to the large number of the Linux distros that were popular about 10 years ago, except that these are much more opinionated and have serious vendor lock-in possibilities since it relates to enterprise. Kubernetes, on the other hand feels like a harmonious and homogeneous sol…
Earlier quoted context omitted.
Like OpenStack?
[This is Craig -- CEO of this new venture, co-founder of K8s (with Joe and Brendan), and person who started CNCF (with Jim Zemlin, and a bunch of community wonks from big tech)] It is a funny you say this. I spent a lot of time looking around the community at what existed before starting CNCF, and agonized over this. We needed to take K8s to foundation so that it wouldn't be a 'Google project'. Google was actually th…
In terms of looking at OpenStack hard; and reaching decisions based on various did you do any reach out to the OpenStack community to actually communicate the things you found or heard or concluded so that the group there (including myself) can actually work on improving itself (or perhaps some of the reasons you stated aren't even correct and the community could have helped you clarify those)? If not then it concerns me that you may have reached conclusions without actually talking with that community (but I don't want to jump to any conclusions without getting your thoughts/input).
So far from looking outwards in on the CNCF and seeing how it compares to the OpenStack community (which I am more involved with, including other small side-communities that I also work in) I've yet to understand what exactly the CNCF is targeting. It seems to be a body that is just adopting various projects that align to some mission (?); I have personally a hard time understanding the reasoning some of the projects have been adopted, maybe you can shed some light on that (what is true north for the CNCF, where is it written down, what is the TOC actually making adoption yes/no decisions on? what criteria? what is the technical taste you talk about, where is it written down?)
The nice thing about OpenStack is that they are writing most/all of this down and agreeing on those kinds of questions in public:
https://github.com/openstack/governance/tree/master/referenc... (github is a mirror, not the source of this repo, but easier for browsing purposes).
Earlier quoted context omitted.
[This is Craig -- CEO of this new venture, co-founder of K8s (with Joe and Brendan), and person who started CNCF (with Jim Zemlin, and a bunch of community wonks from big tech)] It is a funny you say this. I spent a lot of time looking around the community at what existed before starting CNCF, and agonized over this. We needed to take K8s to foundation so that it wouldn't be a 'Google project'. Google was actually th…
So being a PTL in OpenStack I have some various comments and questions that would be nice to have your thoughts on. In terms of looking at OpenStack hard; and reaching decisions based on various did you do any reach out to the OpenStack community to actually communicate the things you found or heard or concluded so that the group there (including myself) can actually work on improving itself (or perhaps some of the r…
The mission of CNCF is the promotion of 'cloud native technologies' -- specifically container packaged, dynamically scheduled, micro-services oriented workloads. It isn't about picking winners, it is about establishing a safe space for innovation and bringing to bear the collective communities. We have legitimately taken some time in getting the identity of the foundation established, but I feel like Dan Kohn (our new ED) is doing super work in creating a collaborative space for new projects.
Earlier quoted context omitted.
So being a PTL in OpenStack I have some various comments and questions that would be nice to have your thoughts on. In terms of looking at OpenStack hard; and reaching decisions based on various did you do any reach out to the OpenStack community to actually communicate the things you found or heard or concluded so that the group there (including myself) can actually work on improving itself (or perhaps some of the r…
A fair point. One thing worth remembering is that this was a point in time thing. I have seen a lot of movement and some very positive signals around convergence of OpenStack, and a real focus on the end user community. When I was doing the digging things felt different and there is a decent chance that were open stack where it is now I would have taken a different position. The mission of CNCF is the promotion of 'c…
Earlier quoted context omitted.
Like OpenStack?
[This is Craig -- CEO of this new venture, co-founder of K8s (with Joe and Brendan), and person who started CNCF (with Jim Zemlin, and a bunch of community wonks from big tech)] It is a funny you say this. I spent a lot of time looking around the community at what existed before starting CNCF, and agonized over this. We needed to take K8s to foundation so that it wouldn't be a 'Google project'. Google was actually th…
1 - the openstack board has 0 technical input to projects - the way to get things done in OpenStack is still to throw developers at it.
This does somewhat push the balance of power to larger companies - they have the money to employ developers.
2 - we have "community directors" who are elected by the people who actually commit code 3 - definite improvement over the initial setup of openstack, but that is currently changing with the User Committee
One question I would have about this - how are the end user groups requirements put forward? what mechanisms is there to ensure developers work on the defined priorities?
4 - Yup - we have the equivalent with the Technical Committee (the TC in OpenStack slang)
Separation of powers is ++ - but how does that play out when the TOC decides that they want to do something that does not mesh with the boards plans?