+1 nb

+1 nb -- Justin Garrison justingarrison.com

+1 nb -- Justin Garrison justingarrison.com

Thanks Quinton for the suggestion. I added some of my feedback here. https://github.com/cncf/toc/pull/163#issuecomment-437167354 -- Justin Garrison justingarrison.com

I'm well aware of the adoption and uses of Harbor. My company runs it and my criticisms come from first hand experience as a user and operator of the software. I'm happy to move my feedback out of thi

-1 nb I understand the need for container registries in a containerized environment, but I'm not sold Harbor being the solution for most people's needs when they need to run their own registry. -- Jus

+1 nb While I agree with the non-definition concerns I also don't think a strict definition is helpful or useful for the CNCF, its communities, or the companies looking to join to support its efforts.

​+1 non-binding​ -- Justin Garrison justingarrison.com

​-1 non-binding I think linkerd does a great job helping applications gain resilience from the network proxy and it has done an amazing 🙌 job and educating users and gaining production usage. I don't

​+1 non-binding​ -- Justin Garrison justingarrison.com

​+1 non-binding​ -- Justin Garrison justingarrison.com

I feel like "secure" is more along the lines of the end goals, not engineered attributes. I agree it's very important (see chapter 8 of Cloud Native Infrastructure) but many of the ways to make someth

​Not at all. Please do! I shared them​ ​so they could be incorporated​​ I agree. Many things can claim to be "scalable" but every design decision has trade-offs. How you get to scalability is what mat

0 non-binding I think the spec is very interesting and necessary but I feel like it, and associated example tooling (SPIRE), may be too early for even inception level -- Justin Garrison justingarrison

I'm glad so many people found my definitions helpful! I disagree that applications have "always been designed for resiliency, operability, and observability". I have worked on numerous systems that ha

This is just my opinion. Feedback is encouraged. I did a lot of thinking about definitions when writing Cloud Native Infrastructure with Kris Nova last year. In the book I define cloud native infrastr

We have version 0.9.6 in the Cloud Native Infrastructure book. The book goes into production today but I'm pretty sure we can swap out the diagram when a new version is available so long as it's avail

I like more community involvement but I think we need clarification on how contributors and ambassadors are different?​ What role does each play and where is there overlap? When signing up to be a con

Speaking of Istio, do we know if there are any plans around istio being donated to the CNCF? How does that affect inclusion of envoy (I'm assuming it doesn't)? I think it's good to have complimentary

I agree this would be a useful group in the cncf but also have concerns discussed in earlier calls about being too early on trying to standardize a solution and possibly limit an evolving technology t