-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project proposal: Istio Service Mesh #70
Conversation
Signed-off-by: Shriram Rajagopalan <shriram@us.ibm.com>
Signed-off-by: Shriram Rajagopalan shriram@us.ibm.com |
+1 |
In my opinion projects should have adoption before being added. This project is so new. Why do you need to be in CNCF? Is it just for status? Foundations, imho, are not for marketing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple changes recommended including changing the incubation level to inception as per requirements set forth https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc
|
||
* https://github.com/istio/istio[https://github.com/istio/istio] + | ||
* https://github.com/istio/api[https://github.com/istio/api] + | ||
* https://github.com/istio/proxy[https://github.com/istio/proxy] + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with the monorepo merge, these repos are no longer accurate.
* Yahoo! | ||
* Apprenda | ||
* Concur | ||
* AT&T |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if it matters, however, the contributor list is much larger.
platform-independent way to connect, manage, and secure microservices. + | ||
|
||
*Sponsor / Advisor from TOC*: Brian Grant + | ||
*Preferred maturity level*: incubating + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The incubation stage requires three real deployments of suitable scope: Reference: https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc
Might consider the inception stage? I suspect after 1.0 is released, incubation will be a nobrainer.
Thanks for the write up. We've been evaluating istio in v0.2 release, there're two major concerns for us to use istio in production.
This makes me wonder what is the scalability limit of istio? I believe v0.3 has improvement around performance and stability (like request is cached in mixer), but I didn't find a published documentation around this. |
@jessfraz the primary reason projects have inception status (applicable for early stage) is to promote collaboration. As you imply this could generate marketing, but is that so bad that inception should be blocked? |
As requested during the November 7th, 2017 CNCF TOC meeting, we submit Istio for consideration to be included in a CNCF project.