CNCF Blog

I don't know how I haven't seen CNCF before, but can you give me (and anyone else who might not know) a brief summary of what they do? Their page makes it clear that I should know, but doesn't give me an obvious place to click to get a clue. EDIT: Found some markety things here. https://www.cncf.io/ ------ What is CNCF? CNCF is an open source software foundation dedicated to making cloud native computing universal and sustainable. Cloud native computing uses an open source software stack to deploy applications as microservices, packaging each part into its own container, and dynamically orchestrating those containers to optimize resource utilization. Cloud native technologies enable software developers to build great products faster.

Why not the Cloud Native Computing Foundation (https://cncf.io)? They manage Kubernetes (cluster orchestration) and recently adopted Prometheus (metric monitoring & alerting). A real-time distributed database as good as RethinkDB could be a great addition, if they are willing to accept it.

Following projects seem promising: * OpenCompute[1]: A Facebook lead initiative to build and design open source hardware, mainly for data centers but also for enterprise. * RISC-V[2]: An open source ISA and alternative to x86 and ARM. * Cloud Native Computing Project[3]: An industry collaboration for building cloud infrastructure. * Teleoperations[4]: Remotely operating machines where humans take over in situations where AI is not sure of the correct action to take. For example, before humans get self-driving vehicles, we may get vehicles that are operated remotely. The vehicle will have cameras that stream the data to operators who could be sitting at an office who in turn send control signals wirelessly to the vehicles. This model could also be applied to drones, humanoid robots etc. More jobs could be sent to low wage economies and workers there could perform work that previously required physical presence in high wage economies. [1] https://www.opencompute.org/ [2] https://riscv.org/ [3] https://www.cncf.io/ [4] https://en.wikipedia.org/wiki/Teleoperation

Love the idea. I'm not sure if anyone has found a sustainable model yet. Looking at the current CNCF landscape, majority of the graduated projects have huge backing from single corps - promoted with the open source labelling. https://www.cncf.io/projects/ i.e. argo by Intuit, Cilium by Cisco, SPIFFE/SPIRE by VMware/HPE

I don’t agree here. There are operators like the one I’m a maintainer of (CloudnativePG) which works directly with Kubernetes, teaching it how to handle Postgres clusters as a coordinated set of instances. Enormous improvements have been done in the last couple of years, and we are particularly focused in working together with storage groups in Kubernetes to handle database workloads, such as for example declarative support for tablespaces and volume snapshots. I suggest you to read CloudnativePG documentation as well as this article: https://www.cncf.io/blog/2023/09/29/recommended-architectures-for-post… Also watch the video of my talk at last Kubecon in Chicago about handling very large databases. I hope this helps.

Provenance is NOT injecting secret data into the build process. Provenance (scoped to supply chain security) is a document that describes the process in which the artifact goes through to become an artifact, to include all steps such as testing, GRC, etc. in-toto is a great way to describe provenance. I talk about it in the CNCF blog article: https://www.cncf.io/blog/2023/08/17/unleashing-in-toto-the-api-of-devs… Disclaimer, I am a member if the in-toto steering committee and the CEO of a software supply chain startup, Testifysec. https://github.com/in-toto/witness is our project

Presumably this: https://www.cncf.io/ Cloud Native Computing Foundation

We are hoping to get WasmEdge running on as many IoT devices as possible … We would love to see more containerization on the edge: https://www.cncf.io/blog/2021/11/11/containerization-on-the-edge/

Then what are foundations like CNCF (https://www.cncf.io/) doing? I'm asking honestly, if there's any difference between CNCF and any other standards governing body.

I didn't know what CNCF is. https://www.cncf.io/ > Cloud Native Computing Foundation (CNCF) serves as the vendor-neutral home for many of the fastest-growing open source projects, including Kubernetes, Prometheus, and Envoy. Does erlang and OTP count by this definition?

My 5yo loves reading the kubernetes book (paperback copy of https://www.cncf.io/the-childrens-illustrated-guide-to-kubernetes/), I found him reading it by himself the other day I guess it has sort of a plot. I think he likes it mostly because I tell him that’s what I do at work.

For anyone else wondering: Cloud Native Compute Foundation https://www.cncf.io/ > a Linux Foundation project that was founded in 2015 to help advance container technology[1] and align the tech industry around its evolution. > It was announced alongside Kubernetes 1.0, an open source container cluster manager, which was contributed to the Linux Foundation by Google as a seed technology. Founding members include Google, CoreOS, Mesosphere, Red Hat, Twitter, Huawei, Intel, Cisco, IBM, Docker, Univa, and VMware -- https://en.wikipedia.org/wiki/Cloud_Native_Computing_Foundation

The unimpeachable approach for the software industry is to setup consortiums to define open standards for APIs, file formats and wire protocols, instead of relying on replicating the most popular proprietary ones. In fact there already exist such consortiums, for example https://www.w3.org, tasked with standardizing WWW, or https://www.cncf.io for cloud computing standards.

The clearest path is to become a Certified Kubernetes Administrator. There are a number of companies currently hiring CKAs. https://www.cncf.io/certification/cka/ https://jobs.cncf.io/ Disclosure: CNCF, which I run, manages the CKA and the job board. But I really have seen many people get great jobs by becoming a CKA.

I can recommend joining the CNCF End User community [1] as it allows exchanging experiences around common problems, e.g. developer experience in a mid/large org, regulatory requirements (there are some banks in the CNCF End User community), etc. For list of current members, see https://www.cncf.io/people/end-user-community/ (I'm working for Zalando and are co-chair of the CNCF End User Developer Experience SIG). The CNCF End User community is a vendor-free zone, so you can also discuss and learn about experiences with certain vendors to have better insights before deciding on one ;-) [1] https://github.com/cncf/enduser-public

I'd wager that nobody would complain if Google donated Go to an open organization such as CNCF [1]. The CNCF is a good fit because it already hosts the world's most prominent Go projects, including Kubernetes and Prometheus. While Google is certainly a big bish in that pond, there are plenty of other big fish to balance them out, including Cisco, Red Hat/CoreOS, Github, IBM, Intel and Docker. Or invent a new organization. Call it "the Go Foundation". Make sure it's independent and has the bylaws and administrative structure to prove it. It's worked out pretty well for Python [2]. [1] https://www.cncf.io/ [2] https://www.python.org/psf-landing/

EKS is no more a competitor to K8S than DOK8s is a competitor to K8s. The CNCF Conformance page[1] shows a link to a spreadsheet[2] which indicates there are currently 96 products by 82 different vendors, including 34 hosted platforms like EKS, which are all Kubernetes. ECS on the other hand, is a so-called "vanilla" container service which provides its own abstractions and offers no suite for conformance, or compatibility with other vendors' offerings. I have not heard lots of people say great things about ECS. If I could say one nice thing, it's that there is probably less to learn about ECS than about Kubernetes. [1]: https://www.cncf.io/certification/software-conformance/ [2]: https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wl…

I'm working on some BYOH cloud based data processing lately soooo....: - Everything sponsored by the CNCF (https://www.cncf.io/) - Everything Hashicorp (https://www.hashicorp.com/) - OpenStack (https://www.openstack.org/) And a small bonus: - Dotmesh (https://dotmesh.com/), snapshot awesomeness

This explains the rationale: https://www.cncf.io/blog/2017/02/01/cncf-recommends-aslv2/

The news in the article is that CNCF spent good money to wipe out a copyleft license. They think history has shown a more permissive license without copyleft or a patent grab (just a patent notice) - namely ASLv2 - is a far superior choice and paid to get that in place. Their very recent explanation is well worth reading: https://www.cncf.io/blog/2017/02/01/cncf-recommends-aslv2 I'll explain what I mean by patent notice since those are my words, quick version: If you don't declare that you have patent rights affecting a portion of code you have contributed, you've given those patent rights.

No business model - Prometheus is 100% free and open-source and independent of any one company. We have also joined the Cloud Native Computing Foundation (https://cncf.io/) as the second member project after Kubernetes: https://cncf.io/news/announcement/2016/05/cloud-native-computing-found… Read more here: https://prometheus.io/docs/introduction/overview/ and here: https://prometheus.io/community/

IMO transparent proxies for observability are not the best pattern. And I speak from experience, we developed the Postgres plugin for Envoy [1], [2] and we use it in StackGres [3], among others, for this very same reason, observability. There's two main problems with said proxies: * Latency. Yes, yes, yes, they add "microseconds" vs "milliseconds for queries", and that's true, but just part of the story. There's an extra hop. There's two extra sets of TCP layers being traversed. If the hop is local (say a sidecar, as we do in StackGres) it adds complexity in its deployment and management (something we solved by automation, but was an extra problem to solve) and consumes resources. If it's a network hop, then adds milliseconds, and not microseconds. * Performance. It's not that hard to write a functioning PG wire proxy (it's not trivial either). But it is extremely hard to make it perform well under high load scenarios. Most of the proxies I have seen crack down under moderate to high performance. What's the solution then? The Postgres extension model to capture the metrics (we also experimented with eBPF, but it causes too many kernel-user space context switches when you can do the same in an extension without them), and a small sidecar to push the metrics out via a standardized protocol like OTEL. [1]: https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/ne… [2]:…

> A better question would be what is the point of CNCF? I ask myself that every time I happen to stroll past CNCF things. I just can't avoid feeling that it's a big cloud complexity racket - and not even a classy one. A constant barrage of expensive conferences, vague memberships [1], and over-the-top certification schemes [2]. Not to even mention the obvious self-interests of hyperscalers of setting up this org in the first place. [1] "The CNCF Silver Membership offers unmatched value across your entire organization. Whether a startup, scale-up, or mid-sized company, get ready to lead, learn, grow, and be recognized in the cloud native ecosystem." https://www.cncf.io/about/join/silver/ [2] "Individuals who have successfully passed every CNCF certification (currently CKA, CKAD, CKS, KCNA, KCSA, PCA, ICA, CCA, CAPA, CGOA, CBA, OTCA, KCA) and LFCS, will receive the title of Golden Kubestronaut for life [...]" https://www.cncf.io/training/kubestronaut/

"Cloud Native" == Kubernetes As in https://www.cncf.io/

The other kinds exists too: https://www.cncf.io/

SEEKING WORK | Remote (Tucson, Arizona) I'm a full-service writer who helps open source && cloud native startups inspire devs and engineering leads to `commit`. For those still forming value propositions and fine-tuning websites, I uplevel the messaging you already have with my unique experience with these technical communities. And for those ready to distribute their proven messaging with content, I write opinionated and technical articles on Kubernetes, GitOps, IaC, pre commit validation and shift left, trace-based testing, APIOps, and much more. I recently authored a report in association with CNCF on end user adoption of cloud native tooling, which gave the unique opportunity to pick the brains of 20 tech leaders at major orgs on platform engineering, tool choice, Kubernetes provisioning, and much more. How can I make this know-how for you? - Initialize a messaging strategy that differentiates your open source project and commercial product as commit-worthy - Load balance your copywriting tasks so you can return to being a founder, leader, and maintainer - Deploy content (both strategy and execution) that builds trust and authority with your strongest opinions backed by your technical prowess If you feel like you can't reach the right people because you don't have the right copy/content, or know where you're headed but can't scale, shoot me an email and we'll find the paved road you've been after. -- - Book a call:…

> Fortunately K8s is _not_ a Google owned project. Yes, there are a lot of Google people involved, but it really is a community project. It was created by Google and then "donated" to CNCF. Conveniently, CNCF doesn't even list its members: https://www.cncf.io/about/members/ According to Wikipedia, though, "Founding members include Google, CoreOS, Mesosphere, Red Hat, Twitter, Huawei, Intel, Cisco, IBM, Docker, Univa, and VMware." [1] Ah yes. I just love that free community spirit. Top 10-15 contributors are all paid money to work on this by Google, RedHat, Microsoft, VMWare, Goldman Sachs (and I couldn't bother to check others). That is, 18 billion net income last quarter, 15 billion net income last quarter, 141 million net income last quarter, 6 billion last quarter... These ginormous corps solve their own problems under the guise of open source, and gullible developers fall for the community promise. [1] https://en.wikipedia.org/wiki/Cloud_Native_Computing_Foundation

> I don't think anyone wants to use Helm. Here is why everyone should use Helm: Helm 2.0 introduced package as a first-class concept for Kubernetes and created the standard to distribute applications, thanks to Helm thousands of people could discover and collaborate on cloud-native deployments of the open source software https://github.com/helm/charts/tree/master/stable published and managed by organizations and contributors all over the world. Helm 3.0 keeps innovating, it adopts the most forward-thinking approach to package management and Kubernetes config management by using higher level domain specific language based on Lua to create expressive package management system: https://sweetcode.io/a-first-look-at-the-helm-3-plan/ Helm is also backed by CNCF[1] and is the best choice so far for organizations to create a reproducible CI/CD pipeline in a Kubernetes cluster. [1] https://www.cncf.io/blog/2018/06/01/cncf-to-host-helm/

Given their recentish argument with the CNCF[0] not sure how much I would trust it. [0] https://www.cncf.io/blog/2025/05/01/protecting-nats-and-the-integrity-…

Reminder - KeyCloak was donated to CNCF so a safe choice https://www.keycloak.org https://www.cncf.io/blog/2023/04/11/keycloak-joins-cncf-as-an-incubati…