text stringlengths 0 1.8k |
|---|
**Emile Vauge:** Everything. You can think about Kubernetes federation, that's one solution to handle several Kubernetes clusters as a management perspective, but also connectivity to those clusters, interconnectivity between those clusters, end-to-end security from users to all those clusters... All those aspects. Hig... |
\[48:02\] So today it's almost impossible to do it simply. I mean, it is impossible to have something simply. You have to gather a gigantic number of software and platforms to make it work, and that's an interesting problem that we want to tackle at Traefik Labs. |
**Gerhard Lazu:** That's a big problem space, and you made me really curious now, so I'll keep an eye. That sounds really interesting. So coming from this big problem space, coming to a smaller problem space - or not problem space, but like a space... Which is your favorite Traefik proxy? Because Traefik is so much mor... |
**Emile Vauge:** In the whole Traefik, reverse proxy - yeah; there are so many aspects... At least we have four categories, I guess. You have the routing, load balancing categories, the security aspect... You said the auto-discovery, the dynamic configuration aspect, I will say... And then finally, the observability as... |
**Gerhard Lazu:** Okay. So this is unexpectedly interesting, and the reason it's unexpectedly interesting is because today we have Ingress NGINX and Cert Manager, which from what I'm hearing, Traefik is handling as a single component. That's interesting. Now, there's a certain requirement that we have with the certific... |
**Emile Vauge:** In theory, Traefik is connecting to the CDN itself. It is configuring itself the CDN, to create the DNS entry, for example, to validate your \[unintelligible 00:50:43.02\] certificate. So you don't have to do anything in that specific use case. |
**Gerhard Lazu:** \[50:50\] I think I'm thinking about getting hold of the values of the public \[unintelligible 00:50:53.01\] and the private key, so that we can upload them to the CDN. Because Cert Manager, that manages the integration with the certificate provider - LetsEncrypt in this case - via DNS, so Cert Manage... |
**Emile Vauge:** Yeah. |
**Gerhard Lazu:** So we synchronize those with a CDN via the API. Because the CDN is running outside of Kubernetes. So Kubernetes is just like our origin... |
**Emile Vauge:** Oh, okay, okay... Because you want to have the same certificate on the CDN. |
**Gerhard Lazu:** Exactly, yes. |
**Emile Vauge:** Okay, okay. So yes, basically you would have to do the same with Traefik. |
**Gerhard Lazu:** Okay. |
**Emile Vauge:** It would work the same, but you would have to do it. |
**Gerhard Lazu:** Okay. So as long as I can access those values, that's all I would need, and that means I would reduce one of the components, or remove one of the components, and simplify the whole setup. I love that. That sounds great. Okay, so one more reason to look at Traefik. Wow, okay. Not that I needed it, but ... |
So as we are wrapping up, as a listener, if I have to remember one thing from this conversation, what would that be? |
**Emile Vauge:** So at Traefik Labs, as we already talked about during this podcast, we have a really strong connection with our community... And this is something I'm extremely proud of. Because first of all, it's not easy, and also, once you succeed in doing that, you get so much from it. So much. You get some feedba... |
So yeah, I would love to encourage people to create this kind of communities even more and more in the future... Because at the end of the day, that's probably the best way to build a successful and useful product for your users. So yeah, that's my take-away. Communities are probably one of the hardest things to build ... |
**Gerhard Lazu:** From my perspective, that is a sign of a true cloud-native company and product. If you believe what you've just said, that's it. Because cloud-native is all about the community, all about the people. That's one of my focuses as well in this -- actually, that's my central focus for this podcast, the pe... |
**Emile Vauge:** Thank you. |
**Gerhard Lazu:** I loved having you. Looking forward to a next time. This was too good. Thank you. |
**Emile Vauge:** Cool. Thank you so much for your time, too. Happy to discuss in the future. |
• KubeCon/CloudNativeCon events |
• Stephen Augustus' experience with recording podcasts from conferences |
• Los Angeles event planning (in-person component) |
• Keynote ideas (game show concept with Bob) |
• Adding a "show" element to keynotes |
• Promotional videos and content impact on the keynote |
• Co-chairs' roles and conference involvement |
• Conference structure and transition of co-chairs |
• The importance of considering the end-user perspective in cloud-native solutions |
• The roles of team members Jasmine, Constance, Stephen, and Gerhard in their respective positions at Twitter and KubeCon EU |
• Constance's role as "the question master" and her approach to observability through questioning |
• Discussion about changes and challenges faced by the team, including personal emergencies and deadlines |
• The creation of a promotional video for KubeCon EU that played on the theme of misinformation in the world |
• Appreciation for the hard work of program chairs and track chairs who review conference talks |
• Challenges of reviewing talks at KubeCon |
• Importance of considering external factors in review process |
• Need for balance when accepting similar talks |
• Observability as a topic example with various takes |
• 101 track focus on beginner content |
• Balance between reviewer feedback and program structure |
• Volume and complexity of the review process |
• Comparison of talk acceptance numbers across different KubeCon events |
• Tips for submitting talks, including differentiation and takeaway identification |
• Importance of reviewing abstracts from multiple perspectives |
• The importance of playing to one's strengths when presenting or sharing information |
• Different learning and communication styles among individuals |
• Benefits of recording oneself and refining presentation skills through internal demos and feedback |
• Various formats for sharing knowledge, such as blog posts, podcasts, and workshops, rather than just talks |
• Recognition and appreciation in the community can come from multiple forms of contribution, not just public speaking |
• Importance of acknowledging and highlighting other types of contributions to a project, beyond public speaking or presentations |
• Hallway track at KubeCon allows attendees to meet others with similar interests and form connections |
• The hallway track is not just about attending talks, but also about networking and having conversations with others |
• Replicating the hallway track experience virtually can be done through Zoom breakout rooms |
• Meeting people in person vs online is a key difference, allowing for more personal connections and deeper discussions |
• The "PacMan rule" suggests expanding social circles to allow new people to join and participate |
• Reiterating community guidelines and rules will be important when transitioning back to in-person events |
• Encouraging community ownership and participation, rather than relying on others to provide updates |
• Responsibility falls on individuals to seek information and updates from communities they participate in. |
• Kubernetes community resources are available on github.com/community for learning about governance, SIGs, and working groups. |
• It's not possible for speakers or organizers to provide all necessary information; attendees should generate their own questions and seek further knowledge. |
• Be kind and respectful when engaging with content, considering the effort and dedication of speakers and organizers. |
• Use official channels for feedback, such as talk surveys, conference surveys, and transparency reports. |
• Constructive criticism is essential for growth and improvement in communities. |
• Assume good intent from others, but also acknowledge historical power imbalances and do your own work to be thoughtful in communication. |
• The importance of community in building and maintaining KubeCon |
• Everyone is responsible for creating a positive and inclusive environment at KubeCon |
• Conducting oneself appropriately according to codes of conduct |
• Recognizing the need to acknowledge and manage negative behaviors within the community |
• Celebrating the unique attitude and inclusivity of the cloud-native landscape and CNCF |
**Gerhard Lazu:** So can you tell that this is my third time that I'm recording this? |
**Stephen Augustus:** Oh, congrats! |
**Gerhard Lazu:** So it's a new podcast, it's all about shipping stuff, and the reason why we are meeting is because you helped ship KubeCon, literally. Every day, you were shipping KubeCon. And whenever it's KubeCon, I like to get the organizers, the people behind the event, and then the co-chairs as well. So this is ... |
**Stephen Augustus:** Thank you. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.