Cloud native as a paradigm involved because people wanted vendor agnostic infra, and a more declarative approach to deploying workloads. @Divya_Mohan02#KubeCon
3 categories of projects in the CNCF: Sandbox, Incubating, and Graduated. Sandbox is early with lots of innovation. Incubating projects are being used in production by more people. Graduated projects are mature and stable. #KubeCon@coffeeartgirl
The landscape is made of up cards for the projects. Cards include the GitHub info, funding, market cap. #KubeCon@kunalstwt
Tools in the landscape fall into categories: App Containerization, Infra provisioning, Container orchestration, Security & Compliance. #KubeCon@SaiyamPathak
We shouldn’t wait to the end to think about security, do it from day zero. #KubeCon
(There are so many observerability tools, wow). You need to use them to get visibility into your infra and workloads. #KubeCon
Other categories include GitOps, Policy, and Service Mesh. #KubeCon
How do you narrow down things when there are multiple projects? Should you use a new project? How do you migrate? Match your requirements with the project’s specs/features. #KubeCon
Think about scaling from the start. Create POCs for the projects you’re comparing. #KubeCon
There’s some CNCF terminologies you should know? CNCF members, end users (consuming the projects), TOC (Technical Oversight Committee), Governing Board (CNCF business decisions). #KubeCon
TAGs focus on projects within a specific domain (networking, multi-tenancy, etc.). #KubeCon
There’s a guide to navigating the landscape on the landscape web site. #KubeCon
Some areas for contributing: infra, code, docs, and even helping with contributor experience. #KubeCon
Kubernetes has a great shadow program if you want to learn more about the roles in the project. Certification is another good way to learn and test your knowledge. #KubeCon
The size of the landscape isn’t a negative thing - these are tools to help us solve problems, like words in a dictionary. #KubeCon
• • •
Missing some Tweet in this thread? You can try to
force a refresh
During my chat last night with @LukasGentele and @fabiankramm, Lukas mentioned what a risk it was for me to join @loft_sh when I did. At that time it was mainly Lukas and Fabian and our designer (who is really rad).
My instinct at the time had actually been to join a very large company. I’d been at three early stage companies in a row and felt like I needed a break. I had never heard of Loft Labs and knew nothing about the founders.
But when I looked at the product I was very impressed. I’d been hearing people in the Kubernetes community complain about multi-tenancy pain for years. Virtual clusters were such a new approach and very smart I thought. (At that point they were in the commercial product only.)