Proposing Istio to become a CNCF project #827
Conversation
craigbox
changed the title
|
@craigbox nicely done! You mentioned transfer of the trademark to LF but also availability under OUC. Would you elaborate on this concept? |
|
|
||
| Licenses for most Istio dependencies are automatically included at https://github.com/istio/istio/tree/master/licenses. A snapshot of modules and their corresponding licenses [can be found below](#licenses). | ||
|
|
||
| Projects in istio-ecosystem will be brought in line with CNCF guidelines before submission. |
There was a problem hiding this comment.
Do these subprojects not have a choice? Presuming they have a choice, isn’t it odd that integrated projects could become sandbox projects without a separate application and oversight?
There was a problem hiding this comment.
There are a types of project in istio-ecosystem:
- contributed projects (e.g. Admiral)
- useful samples, maintained by the Istio project (e.g. wasm-extensions)
- things that are wildly out of date, which will be archived.
For the first two, we will either help the teams move to their own orgs, or if they wish to remain in the "Istio incubator" (similar to the kubernetes-sigs repository, where projects exist but are not granted the same status as the parent project), they will individually need to be updated to meet CNCF standards.
|
Thanks @dzolotusky !! assigned to you. |
amye
moved this from Needs TOC Review & Sponsor
to In Due Diligence
in Incubation Projects Backlog
Very exciting! Congrats everyone!!! |
On behalf of the Istio Steering Committee, please find attached a proposal for Istio to become a CNCF project.
What is Istio?
Istio is an open source service mesh that provides a uniform, efficient and transparent way to secure, connect, and monitor services in cloud native applications. It supports zero-trust networking, policy enforcement, traffic management, load balancing, and monitoring; all without requiring applications to be rewritten.
Istio extends Kubernetes to establish a configurable, application-aware network leveraging the Envoy service proxy. It can manage cloud native and traditional workloads alike, supporting from single-cluster to complex multi-network deployments.
Why are we proposing to join the CNCF?
Istio is taking this step as a mature project, approaching its 5th birthday. At this stage, it has reached a maturity where it can be a major driver for adoption of the cloud native model and ecosystem more broadly.
With the recent acceptance of Knative as an incubating project to the CNCF, we feel that it is the ideal time to join a vendor-neutral home for further community-driven innovation. This includes the ownership of the Istio trademark, which will be transferred to the Linux Foundation. The trademark will remain available for the community to use under the Open Usage Commons' published usage guidelines.
Istio stands on the shoulders of several CNCF projects, such as Kubernetes, Envoy, gRPC, Prometheus and SPIFFE, and many contributors in the Istio community are actively involved with these projects as well. It can be installed with Helm, and integrations exist for many other CNCF projects including Knative, Flagger, Jaeger, Open Policy Agent, and OpenTelemetry. We think that bringing Istio to the CNCF will help accelerate the feedback, feature, and development cycle of not just Istio, but also its partner projects.
Please see the project proposal document for further details.