正在加载视频...

视频加载失败

Kubernetes is the second-largest open-source project in the world. What does it do—and why is it so widely adopted? Kat Cosgrove has led several Kubernetes releases and joined The Pragmatic Engineer podcast to share the history of Kubernetes, how it's built, when it is a good (or not so...

22,268 次观看 • 1 年前 •via X (Twitter)

3 条评论

ryan yang 的头像
ryan yang1 年前

Kubernetes? Orchestrate, scale incrementally—no full rebuilds needed.

SecBriefs | Making Cybersecurity Simple 的头像
SecBriefs | Making Cybersecurity Simple1 年前

⚠️The average person generates 2.5 quintillion bytes of data annually. That's enough to fill 575,000 libraries!📚 This data is used to track, target, and manipulate you. #Cybersecurity matters.💡 Cybersecurity Dictionary for Everyone is on Apple Books:

@bluecow 🐮(schizo) 的头像
@bluecow 🐮(schizo)1 年前

awesome, one day checl my GitHub and model, curious on your opinion

相关视频

Linux is the most widespread operating system, globally – but how is it built? Few people are better to answer this than Greg Kroah-Hartman (Greg K-H): Greg has been a Linux kernel maintainer for 25 years, and one of the 3 Linux Kernel Foundation Fellows (the other two are Linus Torvalds and Shuah Khan). Greg manages the Linux kernel’s stable releases, and is a maintainer of multiple kernel subsystems. We cover the inner workings of Linux kernel development, exploring everything from how changes get implemented to why its community-driven approach produces such reliable software. Greg shares insights about the kernel's unique trust model and makes a case for why engineers should contribute to open-source projects. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you buy: • WorkOS — The modern identity platform for B2B SaaS. • Vanta — Automate compliance and simplify security with Vanta. Check out all of our current sponsor and their offerings: ---- One of the most surprising things I learned about Linux: although 4,000 developers contribute to the project from 500 companies per year, and has around 800 kernel maintainers, the project is run with email, git... and that's about it! No dedicated project managers, no regular meetings across the group. It's a truly fascinating and unique model (and only applies to the Linux kernel project: not to Linux distributions.) We go into more detail about this topic with Greg in the podcast as well.

Gergely Orosz

50,945 次观看 • 1 年前

Why is observability so hard to do well - and so expensive, in general? What is "Observability 2.0" and is Open Telemetry any good? In today's episode of The Pragmatic Engineer Podcast, we answer all of these with Charity Majors , co-author of the O'Reilly book "Observability Engineering," former engineer at Parse/Facebook, and cofounder and CTO at Honeycomb Watch it here: • YouTube: • Apple: • Spotify: • Summary and transcript: Brought to you by our wonderful sponsors - check out their offerings: • Sonar — Trust your developers – verify your AI-generated code. • Vanta — Automate compliance and simplify security with Vanta ---- Topics we cover in this episode: • What is observability? Charity’s take • What is “Observability 2.0?” • Why Charity is a fan of platform teams • Why DevOps is an overloaded term: and probably no longer relevant • What is cardinality? And why does it impact the cost of observability so much? • How OpenTelemetry solves for vendor lock-in • Why Honeycomb wrote its own database • Why having good observability should be a prerequisite to adding AI code or using AI agents • And more! --- My biggest takeaways: 1. The DevOps movement feels like it’s in its final days, having served its purpose. 2. Lots of people get dashboards wrong! Charity doesn’t think that static dashboards are helpful to engineering teams at all. In fact, misusing dashboards is one of the most common observability practices. 3. Observability will be especially important for AI use cases in these ways: a) o11y for LLMs: to get data on how they behave and to be able to debug behaviors. This is relevant for teams building and operating AI models. b) o11y for code generated by AI: the generated code should have the right amount of observability in place. Once the code is deployed to production, developers need to be able to get a sense of how the code is behaving there!

Gergely Orosz

25,485 次观看 • 1 年前

Why did Meta build its own internal developer tooling instead of using industry-standard solutions like GitHub? And what do their systems "Sandcastle," "Landcastle", "Butterflybot" and "Phabricator" do? Tomas Reimers, former Meta engineer and co-founder of Graphite , joins the show to talk about Meta's custom developer tools – many of which were years ahead of the industry. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by our wonderful sponsors: • Swarmia — The engineering intelligence platform for modern software organizations. Start a free trial at • Sentry — Error and performance monitoring for developers. Get 3 months of the Team Plan for free at --- Three of my biggest takeaways from our conversation: 𝟭. “𝗦𝘁𝗮𝗰𝗸𝗲𝗱 𝗱𝗶𝗳𝗳𝘀” 𝗺𝗮𝗸𝗲𝘀 𝗮 𝗹𝗼𝘁 𝗼𝗳 𝘀𝗲𝗻𝘀𝗲 𝗶𝗻𝘀𝗶𝗱𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀. However, it makes less sense when working on, e.g., open source projects. Perhaps this is a reason that GitHub has not added support for this workflow — even though it’s popular inside companies like Meta or Uber. We previously did a deepdive on Stacked Diffs (and why you should know about them). 𝟮. 𝗧𝗵𝗲𝗿𝗲 𝗰𝗼𝘂𝗹𝗱 𝗯𝗲 𝗮𝗻 𝗶𝗻𝗱𝘂𝘀𝘁𝗿𝘆-𝘄𝗶𝗱𝗲 𝗺𝗼𝘃𝗲𝗺𝗲𝗻𝘁 𝘁𝗼 𝗺𝗼𝗻𝗼𝗿𝗲𝗽𝗼𝘀: at mid-sized and larger scaleups and tech companies. Tomas sees a lot of scaleups they work with the move from polyrepos (several repositories) to monorepos. Moving to a monorepo is still a lot of work and requires custom tooling: and this is why it was limited to the largest tech companies in the past. Interesting to hear about this change! 𝟯. 𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴 𝘁𝗼𝗼𝗹𝘀 𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗲 𝘁𝗵𝗲 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝗰𝗲 𝗼𝗳 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗰𝗼𝗱𝗲 𝗿𝗲𝘃𝗶𝗲𝘄𝘀. We’ll see more code churned out by AI: but an engineer needs to review it before it goes out. It’s a good question how we can stick to thorough code reviews when it is so tempting to just say, “Looks good to me (LGTM)” and have the seemingly correct code merged.

Gergely Orosz

37,722 次观看 • 1 年前

This is again a project of an unfathomable scale that's just been completed in China and barely anyone has heard of it in the rest of the world China has just finished constructing a continuous 3,046-kilometer (1,892-mile) green barrier - made of plants and trees - completely encircling the Taklamakan Desert, the world's second-largest shifting sand desert which is about the size of Germany (!). To put this in perspective, this is like building a living wall from Paris to Istanbul, or from Los Angeles to Chicago – except they built it in one of the world's most inhospitable environments. They spent about 40 years building this "green wall". The final 285 kilometers was completed in 2024 on November 28. They built the "wall" with desert-hardy plants like Populus euphratica (desert poplar), Haloxylon (saxaul), and Tamarix (salt cedar), along with innovative sand-control engineering and solar panel installations. The objective of the project is to contain the desert's expansion and to protect surrounding agricultural areas and cities from sandstorms. Before this project, many towns in the region had to be relocated multiple times due to encroaching sand. For instance, the town of Qira in Xinjiang had to move three times in its history, with sand dunes once approaching as close as 1.5 kilometers from the town center. This is easily one of human history's most ambitious and grandest ecological engineering projects. It's insane when you think about it: completely containing a desert the size of Germany! And it's also insane how little attention this has received globally: sadly we've apparently lost the capacity to be impressed by such a project, let alone have the boldness of vision to conceive of one ourselves. All resulting in the fact that whilst China is out there completing 40-year missions to tame entire deserts, we can barely fix potholes in our roads.

Arnaud Bertrand

610,075 次观看 • 1 年前

I'm very pleased to to share that I’ve now completed what I believe to be the most detailed and up-to-date Kubernetes and Cloud Native (KCNA) certification course available 🚀 Dive Into Cloud Native, Containers, Kubernetes and the and the Cloud Native Associate (KCNA). More than a certification course, it’s a transformational journey to becoming a certified Kubernetes professional 🌟 📚 What sets this course apart? This course covers the CNCF's entire KCNA curriculum and more, taking you from the fundamentals to advanced mastery in Containers, Docker, Kubernetes, and Cloud Native technologies. Surpassing the knowledge required to achieve this qualification and providing you with knowledge that will help you in any career. You will also bootstrap the likelihood of success with paths that follow the KCNA such as the CKA, CKAD, Prometheus and GitOps qualifications! 🛠️ Course Features (see the Video for examples): 🖥️ Interactive Hands-On Labs: Dive deep into Kubernetes with our incredible browser-based labs 🎥 In-Depth Video Tutorials: Learn complex concepts through high-quality, engaging videos 📝 Study Tips: Get insider tips before each lesson to maximise your study efficiency ✅ Quizzes: Test your knowledge and reinforce learning at every step 📚 Further Study: Explore beyond the course with curated resources for deeper learning 🏆 3 x Practice Exams: Simulate the real KCNA exam prior to booking to experience to ensure you’re fully prepared! I’m confident that with the comprehensive materials provided that anyone who puts the time and effort in will achieve the Kubernetes and Cloud Native Associate Certification 🏅 🔗 Check out the video for more details. The course is available on my site, and with this announcement I’m excited to continue the early access offer for a small amount of time further! #Kubernetes

James Spurin

14,337 次观看 • 2 年前