Welcome to the Istio community!
This is the starting point for becoming a contributor - improving code, improving docs, giving talks, etc.
Other Documents
- Contributing to Istio - guidelines and advice on becoming a contributor
- Working Groups - describes our various working groups
- Working Group Processes - describes how working groups operate
- Technical Oversight Committee - describes our technical oversight committee
- Steering Committee - describes our steering committee
- Community Roles - describes the roles individuals can assume within the Istio community
- Onboarding Technologies to Istio - how we work to onboard new technologies to the Istio project
- Feature Lifecycle - requirements for features to be labeled Alpha, Beta, or Stable
- Feature Lifecycle Checklist - checklist-form of requirements for features to be labeled Alpha, Beta, or Stable
- Admins for Istio Stuff - lists who handles which part of the Istio infrastructure
- Early Disclosure for Security Vulnerabilities - getting early notification of security vulnerabilities
Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.
Visit istio.io for in-depth information about using Istio.
Istio is an open-source project with an active development community. The project was started by teams from Google and IBM, in partnership with the Envoy team at Lyft.
We have public, recorded, community meetings. They happen on the fourth Thursday of every month at 10 AM US/Pacific. Map that to your local time.
Join this group to have the meetings automatically added to your calendar. You can also find them on the community calendar, along with other major community events.
Meeting agendas and notes can be accessed in the working doc.
Interested in presenting? Please send your abstract to istio-steering@googlegroups.com. This is the information we need from you:
* Name
* Role and Company
* Short Speaker Bio
* Talk title and a short abstract
* Talk Format(Presentation/Demo) and Session Length
* Email to connect
Suitable content:
* Istio new feature releases and project updates
* Tutorials and demos
* Use cases
* Open source content that relates vendor or platform to Istio installation and use
Unsuitable content
* Demos that are disparaging to the Istio project, its functionality or community
* Demos that do not address Istio in any way, including interacting with Istio APIs or interfaces
* Blatant vendor pitches
See our community page for ways to get involved in our community.
To dig deeper, check out the architecture and read some design docs.
If you're looking for something to do to get your feet wet working on Istio, look for GitHub issues marked with the Help Wanted label:
Of course, even if there's not an issue opened for it, we can always use more testing throughout the platform. Similarly, we can always use more docs, richer docs, and insightful docs. Or maybe a cool blog post?
If you've got questions or issues with using Istio, check our discussion board and be sure to connect to our community where there's always someone ready to lend a hand.
If you're a developer trying to hack on or use the Istio code, head to #contributors on the Istio Slack for help.