# Spotlight Published articles for Spotlight. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts DevFeed: [App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-27T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Java](), [App](), [Android](), [iOS](), [Maven]() Tags: [android](), [app](), [build](), [bytecode](), [ios](), [java](), [maven-plugin](), [native](), [shortcuts](), [spotlight]() ### AI overview Codename One App Intents use Java annotations to generate reflection-free handlers for Siri, Spotlight, Shortcuts, Android launcher shortcuts, and internal application commands. The article explains build-time validation, entity parameters, routing, and concurrent handler execution. ### Source excerpt Codename One App Intents generate reflection-free handlers for Siri, Spotlight, Shortcuts, Android launcher shortcuts, and an application command layer from Java annotations. ## Как проект из ШАДа попал в Spotlight статей на конференции ICML 2026 DevFeed: [Как проект из ШАДа попал в Spotlight статей на конференции ICML 2026]() Original publisher: [Read original article]() Author: mightyneighbor (Яндекс) Published: 2026-07-06T07:04:35Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [GPU](), [Graphs](), [Machine learning]() Tags: [2026](), [ai](), [cuda](), [gpu](), [graph](), [icml](), [icml-2026](), [ml](), [research](), [spotlight](), [tag-1e7f0701b819](), [tag-4004cf5948d3]() ### AI overview The article explains why graph neural networks underutilize modern GPUs: their irregular, sparse memory access patterns leave the hardware waiting for data. It describes a project that investigated the problem and produced three families of specialized GPU kernels. The resulting paper, "On Efficient Scaling of GNNs via IO-Aware Layer Implementations," was accepted to ICML 2026 as a Spotlight paper. ### Source excerpt Граф из миллионов вершин не загружает современную GPU на все 100%: видеокарта почти всё время не вычисляет, а ждёт загрузки данных из памяти. Графовые нейросети, или GNN, упираются в это давно: сами операции достаточно простые, но доступ к памяти нерегулярный и разреженный. И чем мощнее GPU, тем заметнее недостаточная её утилизация. Идея выросла из проектного курса в ШАДе. Толчком стало то, что один из самых популярных фреймворков для работы с графами, Deep Graph Library, на момент начала работы не обновлялся уже около года -- это знак того, что в области что-то застряло. Меня зовут Федя Великонивцев, я старший исследователь Yandex Research, руковожу группой, которая занимается эффективными вычислениями на GPU. На том курсе мы с коллегами -- Дарьей Фоминой из команды ML-инфраструктуры Яндекса, Вячеславом Ждановским из команды разработки инференса -- и студентами Даниилом Красильниковым, Алексеем Бойковым и Андреем Долговязовым взялись выяснить, почему графовые нейросети тормозят на современных GPU. Так появился проект, который мы оформили в отдельную статью -- On Efficient Scaling of GNNs via IO-Aware Layer Implementations. Её приняли на ICML-2026 со статусом Spotlight. Для контекста: из 23 918 поданных работ приняли 6 352 (26,6%), а Spotlight достался только 536 работам -- это 2,2% заявок с самыми высокими оценками программного комитета. Дальше расскажу, как мы прошли путь от этого вопроса до трёх семейств специализированных GPU-кернелов -- с парой неожиданных находок по дороге. Читать далее ## Spotlight on WG Device Management DevFeed: [Spotlight on WG Device Management]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-06-24T18:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Hardware](), [Artificial Intelligence]() Tags: [ai](), [hardware](), [kubernetes](), [spotlight]() ### AI overview This Kubernetes spotlight examines the Device Management Working Group and its work on Dynamic Resource Allocation (DRA), which recently graduated to general availability. The article discusses hardware management requirements for GPUs, TPUs, network interfaces, and other specialized resources, along with limitations of the legacy device model and scheduling challenges. ### Source excerpt The rising popularity of AI, Edge, and Telecommunications workloads on Kubernetes has led to new requirements for hardware management. We now need hardware specification beyond CPU time and memory allocations. This includes allocating GPUs, TPUs, network interfaces, and other hardware, sometimes after pod start and occasionally through time-sharing. Efficiently managing this specialized hardware is the mission of the Device Management Working Group . Their cornerstone project, Dynamic Resource Allocation (DRA) , recently graduated to GA, marking a fundamental shift in how the project handles hardware-intensive workloads at scale. In this spotlight, we sit down with working group chairs Kevin Klues , Patrick Ohly , and John Belamaric to discuss the limitations of the legacy device model, the NP-hard challenges of scheduling, and how they're building a more programmable, hardware-aware future for Kubernetes. Introducing Device Management Natalie Fisher: Can you introduce yourself, your role, and how you got involved in the Device Management Working Group? Kevin Klues: My name is Kevin Klues. I am a Distinguished Engineer at NVIDIA. I have been a co-chair of the device management working group since its inception at Kubecon EU 2024. I have also been involved with DRA (the working group's primary deliverable) since its inception in 2019 / 2020. I have also been a kubelet maintainer since 2019, with a focus on its device manager, CPU manager, and topology manager subcomponents. The challenges we saw with using these components for workloads that relied on external accelerators (e.g., GPUs) are what triggered us to start working on DRA in the first place. Patrick Ohly: I am a Principal Engineer at Intel. In Kubernetes, I am a Tech Lead for SIG Testing and SIG Instrumentation and co-chair of the Device Management WG. I was co-chair of the WG Structured Logging and a member of the Steering Committee. Some of my early contributions to Kubernetes include ephemeral CSI volumes ## Community Champion Spotlight: Jason Lee DevFeed: [Community Champion Spotlight: Jason Lee]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2026-04-27T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [pull-requests](), [Framework](), [ui](), [GPU](), [Electron]() Tags: [bug-fixes](), [community](), [components](), [electron](), [framework](), [gpu](), [improvements](), [pull-requests](), [spotlight](), [ui]() ### AI overview Zed spotlights Jason Lee's contributions to its GPU-powered UI framework, including 115 merged pull requests and a component library built for Longbridge Pro. ### Source excerpt 115 PRs, a component library, and a stunning app built with gpui. ## Spotlight on SIG Architecture: API Governance DevFeed: [Spotlight on SIG Architecture: API Governance]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-02-12T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [API Governance](), [Kubernetes](), [API](), [Authentication](), [Authorization](), [OAuth]() Tags: [api-governance](), [apis](), [auth](), [authentication](), [authorization](), [interview](), [kubernetes](), [oauth](), [spotlight]() ### AI overview An interview with Jordan Liggitt, lead of Kubernetes SIG Architecture's API Governance sub-project, discusses his work on Kubernetes authentication and authorization and the sub-project's scope. It explains that Kubernetes APIs include REST APIs as well as command-line flags, configuration files, binary execution, backend communication, and data persistence, with goals of stability and continued innovation. ### Source excerpt This is the fifth interview of a SIG Architecture Spotlight series that covers the different subprojects, and we will be covering SIG Architecture: API Governance . In this SIG Architecture spotlight we talked with Jordan Liggitt , lead of the API Governance sub-project. Introduction FM: Hello Jordan, thank you for your availability. Tell us a bit about yourself, your role and how you got involved in Kubernetes. JL: My name is Jordan Liggitt. I'm a Christian, husband, father of four, software engineer at Google by day, and amateur musician by stealth. I was born in Texas (and still like to claim it as my point of origin), but I've lived in North Carolina for most of my life. I've been working on Kubernetes since 2014. At that time, I was working on authentication and authorization at Red Hat, and my very first pull request to Kubernetes attempted to add an OAuth server to the Kubernetes API server. It never exited work-in-progress status. I ended up going with a different approach that layered on top of the core Kubernetes API server in a different project (spoiler alert: this is foreshadowing), and I closed it without merging six months later. Undeterred by that start, I stayed involved, helped build Kubernetes authentication and authorization capabilities, and got involved in the definition and evolution of the core Kubernetes APIs from early beta APIs, like v1beta3 to v1. I got tagged as an API reviewer in 2016 based on those contributions, and was added as an API approver in 2017. Today, I help lead the API Governance and code organization subprojects for SIG Architecture, and I am a tech lead for SIG Auth. FM: And when did you get specifically involved in the API Governance project? JL: Around 2019. Goals and scope of API Governance FM: How would you describe the main goals and areas of intervention of the subproject? The surface area includes all the various APIs Kubernetes has, and there are APIs that people do not always realize are APIs: command-line flags, ## Spotlight on the Kubernetes Steering Committee DevFeed: [Spotlight on the Kubernetes Steering Committee]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2025-09-22T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Open Source]() Tags: [interview](), [kubernetes](), [open-source](), [spotlight]() ### AI overview An interview with Kubernetes Steering Committee members discusses the committee's responsibilities, organizational challenges, contributor support, motivations, and future outlook. The article notes that the interview was conducted in August 2024 and may not reflect the committee's current composition. ### Source excerpt This interview was conducted in August 2024, and due to the dynamic nature of the Steering Committee membership and election process it might not represent the actual composition accurately. The topics covered are, however, overwhelmingly relevant to understand its scope of work. As we approach the Steering Committee elections, it provides useful insights into the workings of the Committee. The Kubernetes Steering Committee is the backbone of the Kubernetes project, ensuring that its vibrant community and governance structures operate smoothly and effectively. While the technical brilliance of Kubernetes is often spotlighted through its Special Interest Groups (SIGs) and Working Groups (WGs) , the unsung heroes quietly steering the ship are the members of the Steering Committee. They tackle complex organizational challenges, empower contributors, and foster the thriving open source ecosystem that Kubernetes is celebrated for. But what does it really take to lead one of the world's largest open source communities? What are the hidden challenges, and what drives these individuals to dedicate their time and effort to such an impactful role? In this exclusive conversation, we sit down with current Steering Committee (SC) members -- Ben, Nabarun, Paco, Patrick, and Maciej -- to uncover the rewarding, and sometimes demanding, realities of steering Kubernetes. From their personal journeys and motivations to the committee's vital responsibilities and future outlook, this Spotlight offers a rare behind-the-scenes glimpse into the people who keep Kubernetes on course. Introductions Sandipan: Can you tell us a little bit about yourself? Ben: Hi, I'm Benjamin Elder , also known as BenTheElder. I started in Kubernetes as a Google Summer of Code student in 2015 and have been working at Google in the space since 2017. I have contributed a lot to many areas but especially build, CI, test tooling, etc. My favorite project so far was building KIND . I have been on the release team, a c ## Spotlight on SIG Apps DevFeed: [Spotlight on SIG Apps]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2025-03-12T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Development](), [Deployment](), [Command-line interface]() Tags: [applications](), [controllers](), [interview](), [kubernetes](), [spotlight]() ### AI overview An interview with the chairs and tech leads of Kubernetes SIG Apps about the group's mission, leadership, and work on developing, deploying, and operating applications on Kubernetes. The discussion also covers controllers and challenges from running AI-related workloads. ### Source excerpt In our ongoing SIG Spotlight series, we dive into the heart of the Kubernetes project by talking to the leaders of its various Special Interest Groups (SIGs). This time, we focus on SIG Apps , the group responsible for everything related to developing, deploying, and operating applications on Kubernetes. Sandipan Panda (DevZero ) had the opportunity to interview Maciej Szulik (Defense Unicorns ) and Janet Kuo (Google ), the chairs and tech leads of SIG Apps. They shared their experiences, challenges, and visions for the future of application management within the Kubernetes ecosystem. Introductions Sandipan: Hello, could you start by telling us a bit about yourself, your role, and your journey within the Kubernetes community that led to your current roles in SIG Apps? Maciej: Hey, my name is Maciej, and I'm one of the leads for SIG Apps. Aside from this role, you can also find me helping SIG CLI and also being one of the Steering Committee members. I've been contributing to Kubernetes since late 2014 in various areas, including controllers, apiserver, and kubectl. Janet: Certainly! I'm Janet, a Staff Software Engineer at Google, and I've been deeply involved with the Kubernetes project since its early days, even before the 1.0 launch in 2015. It's been an amazing journey! My current role within the Kubernetes community is one of the chairs and tech leads of SIG Apps. My journey with SIG Apps started organically. I started with building the Deployment API and adding rolling update functionalities. I naturally gravitated towards SIG Apps and became increasingly involved. Over time, I took on more responsibilities, culminating in my current leadership roles. About SIG Apps All following answers were jointly provided by Maciej and Janet. Sandipan: For those unfamiliar, could you provide an overview of SIG Apps' mission and objectives? What key problems does it aim to solve within the Kubernetes ecosystem? As described in our charter , we cover a broad area related to de ## Where Do I Start With SASE Evaluations? Gartner® Report DevFeed: [Where Do I Start With SASE Evaluations? Gartner® Report]() Original publisher: [Read original article]() Author: Yuval Yatskan Published: 2024-09-10T08:00:00Z Content type: article Language: en Sources: [OpenDNS]() Topics: [SASE](), [Security](), [SD-WAN]() Tags: [cisco-sase](), [risk-management](), [sase](), [sd-wan](), [secure-access-service-edge](), [secure-access-service-edge-sase](), [security-service-edge-sse](), [spotlight](), [strategy]() ### AI overview This Cisco Umbrella article explains how SASE combines cloud-delivered networking and security for distributed workplaces, with SSE as its security-focused subset. It highlights a Gartner report that offers guidance for beginning SASE evaluations, including strategy and requirements considerations. ### Source excerpt Ransomware makes up 154 million of the threats Cisco blocks monthly; information stealers make up 246 million more. However, the continued evolution of online threats from ransomware and persistent bad actors is only one small piece of the risk management puzzle. Security leaders are not only responding to more sophisticated and expanding threats, but they're [...] The post Where Do I Start With SASE Evaluations? Gartner® Report appeared first on Cisco Umbrella. ## Spotlight on SIG API Machinery DevFeed: [Spotlight on SIG API Machinery]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2024-08-07T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [API](), [schema-evolution](), [Back end](), [Front end]() Tags: [api](), [backend](), [frontend](), [kubernetes](), [schema](), [schema-evolution](), [spotlight]() ### AI overview An interview with Federico Bongiovanni and David Eads, chairs of Kubernetes SIG API Machinery, explores the group's scope and responsibilities. They discuss the kube-apiserver, backend storage contracts, API schema evolution, serialization, client and controller patterns, and the importance of avoiding regressions or incompatible changes in the Kubernetes control plane. ### Source excerpt We recently talked with Federico Bongiovanni (Google) and David Eads (Red Hat), Chairs of SIG API Machinery, to know a bit more about this Kubernetes Special Interest Group. Introductions Frederico (FSM): Hello, and thank your for your time. To start with, could you tell us about yourselves and how you got involved in Kubernetes? David: I started working on OpenShift (the Red Hat distribution of Kubernetes) in the fall of 2014 and got involved pretty quickly in API Machinery. My first PRs were fixing kube-apiserver error messages and from there I branched out to kubectl (kubeconfigs are my fault!), auth (RBAC and *Review APIs are ports from OpenShift), apps (workqueues and sharedinformers for example). Don't tell the others, but API Machinery is still my favorite :) Federico: I was not as early in Kubernetes as David, but now it's been more than six years. At my previous company we were starting to use Kubernetes for our own products, and when I came across the opportunity to work directly with Kubernetes I left everything and boarded the ship (no pun intended). I joined Google and Kubernetes in early 2018, and have been involved since. SIG Machinery's scope FSM: It only takes a quick look at the SIG API Machinery charter to see that it has quite a significant scope, nothing less than the Kubernetes control plane. Could you describe this scope in your own words? David: We own the kube-apiserver and how to efficiently use it. On the backend, that includes its contract with backend storage and how it allows API schema evolution over time. On the frontend, that includes schema best practices, serialization, client patterns, and controller patterns on top of all of it. Federico: Kubernetes has a lot of different components, but the control plane has a really critical mission: it's your communication layer with the cluster and also owns all the extensibility mechanisms that make Kubernetes so powerful. We can't make mistakes like a regression, or an incompatible change, ## Cisco Umbrella: A Leader in the GigaOm Radar for DNS Security DevFeed: [Cisco Umbrella: A Leader in the GigaOm Radar for DNS Security]() Original publisher: [Read original article]() Author: Negisa Taymourian Published: 2024-06-26T08:00:00Z Content type: news Language: en Sources: [OpenDNS]() Topics: [Cisco](), [Security](), [Scalability](), [Cloud](), [data centers]() Tags: [cisco](), [cloud](), [data-centers](), [dns](), [dns-layer-security](), [dns-security](), [gigaom-radar](), [products-services](), [radar](), [report](), [routing](), [scalability](), [security](), [spotlight](), [webinar]() ### AI overview Cisco Umbrella was recognized as a leader in the 2024 GigaOm Radar for DNS Security. The article summarizes the report's evaluation of 11 DNS security solutions and highlights Umbrella's flexibility, scalability, security, support, prediction capabilities, and integration. ### Source excerpt GigaOm analysts placed Cisco Umbrella as a GigaOm Radar DNS leader in security, scalability, support and more! Learn what sets Cisco Umbrella apart. The post Cisco Umbrella: A Leader in the GigaOm Radar for DNS Security appeared first on Cisco Umbrella. ## Spotlight on SIG Release (Release Team Subproject) DevFeed: [Spotlight on SIG Release (Release Team Subproject)]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2024-01-15T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Development](), [releases](), [Release notes](), [Testing]() Tags: [community](), [development](), [engineering](), [kubernetes](), [release-notes](), [spotlight](), [testing]() ### AI overview This interview-style article profiles the Kubernetes SIG Release Team and explains how Kubernetes release planning, onboarding, scheduling, testing, code freezes, and release artifacts are coordinated. It also describes how contributors can get involved. ### Source excerpt The Release Special Interest Group (SIG Release), where Kubernetes sharpens its blade with cutting-edge features and bug fixes every 4 months. Have you ever considered how such a big project like Kubernetes manages its timeline so efficiently to release its new version, or how the internal workings of the Release Team look like? If you're curious about these questions or want to know more and get involved with the work SIG Release does, read on! SIG Release plays a crucial role in the development and evolution of Kubernetes. Its primary responsibility is to manage the release process of new versions of Kubernetes. It operates on a regular release cycle, typically every three to four months . During this cycle, the Kubernetes Release Team works closely with other SIGs and contributors to ensure a smooth and well-coordinated release. This includes planning the release schedule, setting deadlines for code freeze and testing phases, as well as creating release artefacts like binaries, documentation, and release notes. Before you read further, it is important to note that there are two subprojects under SIG Release - Release Engineering and Release Team. In this blog post, Nitish Kumar interviews Verónica López (PlanetScale), Technical Lead of SIG Release, with the spotlight on the Release Team subproject, how the release process looks like, and ways to get involved. What is the typical release process for a new version of Kubernetes, from initial planning to the final release? Are there any specific methodologies and tools that you use to ensure a smooth release? The release process for a new Kubernetes version is a well-structured and community-driven effort. There are no specific methodologies or tools as such that we follow, except a calendar with a series of steps to keep things organised. The complete release process looks like this: Release Team Onboarding: We start with the formation of a Release Team, which includes volunteers from the Kubernetes community who w ## Apollo Client 3.9 Feature Spotlight - The memory story DevFeed: [Apollo Client 3.9 Feature Spotlight - The memory story]() Original publisher: [Read original article]() Author: Lenz Weber-Tronic Published: 2023-12-20T16:02:32Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [Memory Leaks](), [Caching](), [Open Source](), [Maintainers]() Tags: [apollo-client](), [cache](), [feature](), [issue](), [leak](), [memory](), [memory-leak](), [memory-leaks](), [open-source](), [spotlight]() ### AI overview Apollo Client 3.9 is released in beta with fixes for various memory leaks, more granular control over internal cache sizes, and deprecation of canonizeResults because of a conceptual, non-fixable memory leak. The article also asks users to help determine appropriate default cache sizes. ### Source excerpt Apollo Client 3.9 is out in beta now, and it fixes various memory leaks, adds granular control over internal cache sizes, and deprecates the canonizeResults option due to a conceptual and non-fixable memory leak associated with it. We want your help to find the correct default cache sizes - see the last paragraph for details on that. The memory story Sometimes, in an open source project, you have that issue that sticks around for a long time because it's not clear how you would tackle it. ## Spotlight on SIG Architecture: Production Readiness DevFeed: [Spotlight on SIG Architecture: Production Readiness]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-11-02T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Architecture & Design](), [Kubernetes](), [Scalability](), [Google]() Tags: [architecture](), [interview](), [kubernetes](), [scalability](), [spotlight](), [technical]() ### AI overview An interview with Wojciech Tyczynski about Kubernetes SIG Architecture's Production Readiness subproject. The discussion covers his work on Kubernetes scalability, including support for 5,000-node clusters, and the need to consider scalability and reliability when designing new APIs, contracts, and features. ### Source excerpt This is the second interview of a SIG Architecture Spotlight series that will cover the different subprojects. In this blog, we will cover the SIG Architecture: Production Readiness subproject . In this SIG Architecture spotlight, we talked with Wojciech Tyczynski (Google), lead of the Production Readiness subproject. About SIG Architecture and the Production Readiness subproject Frederico (FSM): Hello Wojciech, could you tell us a bit about yourself, your role and how you got involved in Kubernetes? Wojciech Tyczynski (WT): I started contributing to Kubernetes in January 2015. At that time, Google (where I was and still am working) decided to start a Kubernetes team in the Warsaw office (in addition to already existing teams in California and Seattle). I was lucky enough to be one of the seeding engineers for that team. After two months of onboarding and helping with different tasks across the project towards 1.0 launch, I took ownership of the scalability area and I was leading Kubernetes to support clusters with 5000 nodes. I'm still involved in SIG Scalability as its Technical Lead. That was the start of a journey since scalability is such a cross-cutting topic, and I started contributing to many other areas including, over time, to SIG Architecture. FSM: In SIG Architecture, why specifically the Production Readiness subproject? Was it something you had in mind from the start, or was it an unexpected consequence of your initial involvement in scalability? WT: After reaching that milestone of Kubernetes supporting 5000-node clusters , one of the goals was to ensure that Kubernetes would not degrade its scalability properties over time. While non-scalable implementation is always fixable, designing non-scalable APIs or contracts is problematic. I was looking for a way to ensure that people are thinking about scalability when they create new features and capabilities without introducing too much overhead. This is when I joined forces with John Belamaric and David E ## Spotlight on SIG Architecture: Conformance DevFeed: [Spotlight on SIG Architecture: Conformance]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-10-05T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Testing]() Tags: [africa](), [community](), [covid](), [developers](), [kubernetes](), [new-zealand](), [spotlight](), [technical](), [testing](), [tests]() ### AI overview An interview spotlighting Kubernetes SIG Architecture's Conformance subproject. It describes the team's work managing conformance-testing technical debt, writing tests, coordinating with SIGs that own untested APIs, and supporting compatibility with the Kubernetes specification. ### Source excerpt This is the first interview of a SIG Architecture Spotlight series that will cover the different subprojects. We start with the SIG Architecture: Conformance subproject In this SIG Architecture spotlight, we talked with Riaan Kleinhans (ii-Team), Lead for the Conformance sub-project . About SIG Architecture and the Conformance subproject Frederico (FSM): Hello Riaan, and welcome! For starters, tell us a bit about yourself, your role and how you got involved in Kubernetes. Riaan Kleinhans (RK): Hi! My name is Riaan Kleinhans and I live in South Africa. I am the Project manager for the ii-Team in New Zealand. When I joined ii the plan was to move to New Zealand in April 2020 and then Covid happened. Fortunately, being a flexible and dynamic team we were able to make it work remotely and in very different time zones. The ii.nz team have been tasked with managing the Kubernetes Conformance testing technical debt and writing tests to clear the technical debt. I stepped into the role of project manager to be the link between monitoring, test writing and the community. Through that work I had the privilege of meeting the late Dan Kohn in those first months, his enthusiasm about the work we were doing was a great inspiration. FSM: Thank you - so, your involvement in SIG Architecture started because of the conformance work? RK: SIG Architecture is the home for the Kubernetes Conformance subproject. Initially, most of my interactions were directly with SIG Architecture through the Conformance sub-project. However, as we began organizing the work by SIG, we started engaging directly with each individual SIG. These engagements with the SIGs that own the untested APIs have helped us accelerate our work. FSM: How would you describe the main goals and areas of intervention of the Conformance sub-project? RM: The Kubernetes Conformance sub-project focuses on guaranteeing compatibility and adherence to the Kubernetes specification by developing and maintaining a comprehensive confor ## Switching between apps using shortcuts on macOS DevFeed: [Switching between apps using shortcuts on macOS]() Original publisher: [Read original article]() Published: 2023-08-22T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [macOS](), [App](), [keyboard]() Tags: [keyboard](), [macos](), [shortcuts](), [spotlight](), [switching]() ### AI overview A developer explains how to switch between frequently used apps on macOS with custom keyboard shortcuts. The approach remaps the right Command key as a Hyper key using Karabiner and assigns shortcuts in Raycast, with BetterTouchTool offered as an alternative. ### Source excerpt This is one of the most common activities when working on a computer. To make it as seamless as possible, I assigned a custom shortcut for every app I commonly use. ## Spotlight on SIG ContribEx DevFeed: [Spotlight on SIG ContribEx]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-08-14T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [devrel](), [pull-requests](), [Latency]() Tags: [blog](), [collaboration](), [communication](), [community](), [devrel](), [kubernetes](), [latency](), [mentorship](), [pull-requests](), [spotlight]() ### AI overview An interview examines Kubernetes' SIG ContribEx, which works to improve contributor experience through guidelines, tools, processes, community support, outreach, and mentorship. It also discusses the group's initiatives and ways to contribute. ### Source excerpt Author: Fyka Ansari Welcome to the world of Kubernetes and its vibrant contributor community! In this blog post, we'll be shining a spotlight on the Special Interest Group for Contributor Experience (SIG ContribEx), an essential component of the Kubernetes project. SIG ContribEx in Kubernetes is responsible for developing and maintaining a healthy and productive community of contributors to the project. This involves identifying and addressing bottlenecks that may hinder the project's growth and feature velocity, such as pull request latency and the number of open pull requests and issues. SIG ContribEx works to improve the overall contributor experience by creating and maintaining guidelines, tools, and processes that facilitate collaboration and communication among contributors. They also focus on community building and support, including outreach programs and mentorship initiatives to onboard and retain new contributors. Ultimately, the role of SIG ContribEx is to foster a welcoming and inclusive environment that encourages contribution and supports the long-term sustainability of the Kubernetes project. In this blog post, Fyka Ansari interviews Kaslin Fields , a DevRel Engineer at Google, who is a chair of SIG ContribEx, and Madhav Jivrajani , a Software Engineer at VMWare who serves as a SIG ContribEx Tech Lead. This interview covers various aspects of SIG ContribEx, including current initiatives, exciting developments, and how interested individuals can get involved and contribute to the group. It provides valuable insights into the workings of SIG ContribEx and highlights the importance of its role in the Kubernetes ecosystem. Introductions Fyka: Let's start by diving into your background and how you got involved in the Kubernetes ecosystem. Can you tell us more about that journey? Kaslin: I first got involved in the Kubernetes ecosystem through my mentor, Jonathan Rippy, who introduced me to containers during my early days in tech. Eventually, I transitioned ## Supporter spotlight: Simon Butler on business adoption of Reproducible Builds DevFeed: [Supporter spotlight: Simon Butler on business adoption of Reproducible Builds]() Original publisher: [Read original article]() Published: 2023-08-01T11:00:00Z Content type: article Language: en Sources: [reproducible-builds.org]() Topics: [reproducible builds](), [Open Source](), [Software Engineering](), [data](), [Internet of things]() Tags: [adoption](), [builds](), [open-source](), [org](), [reproducible-builds](), [research](), [software-engineering](), [spotlight]() ### AI overview This supporter spotlight interviews Simon Butler, a software engineering researcher at the University of Skövde, about a collaborative project with six Swedish businesses that use open source software. The project's paper examines the businesses' knowledge of, experience with, and perceived value of Reproducible Builds. ### Source excerpt The Reproducible Builds project relies on several projects, supporters and sponsors for financial support, but they are also valued as ambassadors who spread the word about our project and the work that we do. This is the seventh instalment in a series featuring the projects, companies and individuals who support the Reproducible Builds project. We started this series by featuring the Civil Infrastructure Platform project, and followed this up with a post about the Ford Foundation as well as recent ones about ARDC, the Google Open Source Security Team (GOSST), Bootstrappable Builds, the F-Droid project and David A. Wheeler. Today, however, we will be talking with Simon Butler, an associate senior lecturer in the School of Informatics at the University of Skövde, where he undertakes research in software engineering that focuses on IoT and open source software, and contributes to the teaching of computer science to undergraduates. Chris: For those who have not heard of it before, can you tell us more about the School of Informatics at Skövde University? Simon: Certainly, but I may be a little long-winded. Skövde is a city in the area between the two large lakes in southern Sweden. The city is a busy place. Skövde is home to the regional hospital, some of Volvo's manufacturing facilities, two regiments of the Swedish defence force, a lot of businesses in the Swedish computer games industry, other tech companies and more. The University of Skövde is relatively small. Sweden's large land area and low population density mean that regional centres such as Skövde are important and local universities support businesses by training new staff and supporting innovation. The School of Informatics has two divisions. One focuses on teaching and researching computer games. The other division encompasses a wider range of teaching and research, including computer science, web development, computer security, network administration, data science and so on. Chris: You recently had a ope ## Spotlight on SIG CLI DevFeed: [Spotlight on SIG CLI]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-07-20T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [kubectl](), [Command-line interface](), [Tooling](), [interoperability](), [Cloud Native Ecosystem]() Tags: [cli](), [cloud-native-ecosystem](), [interoperability](), [kubectl](), [kubernetes](), [spotlight](), [tech-lead](), [tooling]() ### AI overview An interview with SIG CLI leaders describes the group's role in improving Kubernetes command-line tooling, including kubectl, and supporting contributors. It covers the group's goals, ongoing efforts, CLI libraries, and interoperability specifications for Kubernetes-related tooling. ### Source excerpt In the world of Kubernetes, managing containerized applications at scale requires powerful and efficient tools. The command-line interface (CLI) is an integral part of any developer or operator's toolkit, offering a convenient and flexible way to interact with a Kubernetes cluster. SIG CLI plays a crucial role in improving the Kubernetes CLI experience by focusing on the development and enhancement of kubectl, the primary command-line tool for Kubernetes. In this SIG CLI Spotlight, Arpit Agrawal, SIG ContribEx-Comms team member, talked with Katrina Verey , Tech Lead & Chair of SIG CLI,and Maciej Szulik , SIG CLI Batch Lead, about SIG CLI, current projects, challenges and how anyone can get involved. So, whether you are a seasoned Kubernetes enthusiast or just getting started, understanding the significance of SIG CLI will undoubtedly enhance your Kubernetes journey. Introductions Arpit: Could you tell us a bit about yourself, your role, and how you got involved in SIG CLI? Maciej: I'm one of the technical leads for SIG-CLI. I was working on Kubernetes in multiple areas since 2014, and in 2018 I got appointed a lead. Katrina: I've been working with Kubernetes as an end-user since 2016, but it was only in late 2019 that I discovered how well SIG CLI aligned with my experience from internal projects. I started regularly attending meetings and made a few small PRs, and by 2021 I was working more deeply with the Kustomize team specifically. Later that year, I was appointed to my current roles as subproject owner for Kustomize and KRM Functions, and as SIG CLI Tech Lead and Chair. About SIG CLI Arpit: Thank you! Could you share with us the purpose and goals of SIG CLI? Maciej: Our charter has the most detailed description, but in few words, we handle all CLI tooling that helps you manage your Kubernetes manifests and interact with your Kubernetes clusters. Arpit: I see. And how does SIG CLI work to promote best-practices for CLI development and usage in the cloud native e ## The Perfect Blend: Qdoba's SASE Transformation DevFeed: [The Perfect Blend: Qdoba's SASE Transformation]() Original publisher: [Read original article]() Author: William Mabon Published: 2023-05-30T08:00:00Z Content type: article Language: en Sources: [OpenDNS]() Topics: [Cloudflare One](), [Cisco](), [SD-WAN](), [Network](), [Cloud](), [Security]() Tags: [6sense-product-sig](), [cisco](), [cloud](), [customer-focus](), [customer-story](), [meraki](), [network](), [sase](), [sd-wan](), [security](), [security-heroes](), [spotlight]() ### AI overview A Qdoba customer story describes replacing an outsourced, fragmented network and security setup with a centrally managed SASE solution using Cisco Umbrella and Meraki SD-WAN. The company reports lower support costs, faster issue resolution, simpler management, pre-provisioned new sites, and improved network uptime. ### Source excerpt Qdoba customer story highlights (2:00) Grab a burrito, settle in, and learn how Qdoba Mexican Eats revamped its security and network with cloud-delivered magic. It's a spicy story: Qdoba's support costs alone have been slashed by over $300,000 per year, while security posture and uptime are dramatically improved. "When Qdoba is connected, we are [...] The post The Perfect Blend: Qdoba's SASE Transformation appeared first on Cisco Umbrella. ## Spotlight on SIG Instrumentation DevFeed: [Spotlight on SIG Instrumentation]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-02-03T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Instrumentation](), [telemetry](), [Kubernetes](), [observability](), [site-reliability-engineering](), [API]() Tags: [instrumentation](), [kubernetes](), [logs](), [metrics](), [observability](), [spotlight](), [sre](), [tracing]() ### AI overview This SIG Instrumentation spotlight explains how Kubernetes contributors work on observability across Kubernetes components, including metrics, logs, and tracing. Interviews with SIG chairs describe the group's organization, challenges with metrics, and ways to participate and contribute. ### Source excerpt Observability requires the right data at the right time for the right consumer (human or piece of software) to make the right decision. In the context of Kubernetes, having best practices for cluster observability across all Kubernetes components is crucial. SIG Instrumentation helps to address this issue by providing best practices and tools that all other SIGs use to instrument Kubernetes components-like the API server, scheduler, kubelet and kube-controller-manager. In this SIG Instrumentation spotlight, Imran Noor Mohamed , SIG ContribEx-Comms tech lead talked with Elana Hashman , and Han Kang , chairs of SIG Instrumentation, on how the SIG is organized, what are the current challenges and how anyone can get involved and contribute. About SIG Instrumentation Imran (INM): Hello, thank you for the opportunity of learning more about SIG Instrumentation. Could you tell us a bit about yourself, your role, and how you got involved in SIG Instrumentation? Han (HK): I started in SIG Instrumentation in 2018, and became a chair in 2020. I primarily got involved with SIG instrumentation due to a number of upstream issues with metrics which ended up affecting GKE in bad ways. As a result, we ended up launching an initiative to stabilize our metrics and make metrics a proper API. Elana (EH): I also joined SIG Instrumentation in 2018 and became a chair at the same time as Han. I was working as a site reliability engineer (SRE) on bare metal Kubernetes clusters and was working to build out our observability stack. I encountered some issues with label joins where Kubernetes metrics didn't match kube-state-metrics (KSM ) and started participating in SIG meetings to improve things. I helped test performance improvements to kube-state-metrics and ultimately coauthored a KEP for overhauling metrics in the 1.14 release to improve usability. Imran (INM): Interesting! Does that mean SIG Instrumentation involves a lot of plumbing? Han (HK): I wouldn't say it involves a ton of plumbing, ## Developer Spotlight: Reference Health DevFeed: [Developer Spotlight: Reference Health]() Original publisher: [Read original article]() Author: Roberto Annunziata Published: 2023-01-17T05:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [GitHub](), [Binance](), [SDKs](), [API](), [App]() Tags: [api](), [apis](), [developer](), [developer-platform](), [developers](), [health-care](), [payment](), [payments](), [platform](), [sdks](), [services](), [spotlight]() ### AI overview This developer spotlight describes Reference Health, a platform that helps health care providers accept Square payments through electronic medical records and patient portals. Its co-founder explains how Square SDKs, APIs, and PCI-compliant payments supported the product's development and helped automate operations. ### Source excerpt Empowering health care providers with a secure omnichannel payment platform ## Developer Spotlight: Payable Forms DevFeed: [Developer Spotlight: Payable Forms]() Original publisher: [Read original article]() Author: Joan Mweu Published: 2022-07-29T19:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [App](), [Low code](), [Automation](), [SDKs](), [Tooling](), [Google]() Tags: [apis](), [app](), [automation](), [business](), [developer](), [google](), [low-code](), [payments](), [sdk](), [small-business](), [spotlight](), [tooling](), [tools]() ### AI overview This Developer Spotlight profiles Payable Forms, a low-code app for small businesses that connects forms, subscriptions, automations, and payments. Its founder discusses choosing Square, onboarding sellers, and using Web Payments SDK for Afterpay and Cash App Pay integrations. ### Source excerpt Bringing the power of payments to small business tools ## NIST Brings Threat Modeling into the Spotlight DevFeed: [NIST Brings Threat Modeling into the Spotlight]() Original publisher: [Read original article]() Author: Adam Published: 2021-09-23T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [standard](), [Code]() Tags: [article](), [code](), [nist](), [post](), [spotlight](), [standard](), [verification]() ### AI overview This post announces a Dark Reading article about NIST and threat modeling. It mentions NIST releasing a minimum standard for vendor or developer verification of code in July. ### Source excerpt New at Darkreading, a post on NIST and threat modeling ## Developer Spotlight: AuctionZoom DevFeed: [Developer Spotlight: AuctionZoom]() Original publisher: [Read original article]() Author: Richard Moot Published: 2020-03-12T19:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [App](), [Database](), [Android](), [iOS](), [API](), [SDKs](), [OAuth]() Tags: [android](), [api](), [apis](), [app](), [charity](), [database](), [developer](), [ios](), [oauth](), [sdk](), [spotlight]() ### AI overview This Developer Spotlight interviews AuctionZoom CEO John Foster about Bidstation, a system for managing charity auction events. Bidstation helps organizations register bidders, track winning bids, generate invoices, and process payments while integrating with Square. ### Source excerpt Getting charity auction events running smoothly with AuctionZoom [Next page]()