web02.fireside.fm Thu, 16 Apr 2026 01:15:37 -0500 Fireside (https://fireside.fm) TechSNAP - Episodes Tagged with “Storage” https://techsnap.systems/tags/storage Fri, 29 May 2020 00:15:00 -0700 Systems, Network, and Administration Podcast. Every two weeks TechSNAP covers the stories that impact those of us in the tech industry, and all of us that follow it. Every episode we dedicate a portion of the show to answer audience questions, discuss best practices, and solving your problems. en-us episodic Systems, Network, and Administration Podcast. Jupiter Broadcasting Systems, Network, and Administration Podcast. Every two weeks TechSNAP covers the stories that impact those of us in the tech industry, and all of us that follow it. Every episode we dedicate a portion of the show to answer audience questions, discuss best practices, and solving your problems. no Jupiter Broadcasting chris@jupiterbroadcasting.com 430: All Good Things https://techsnap.systems/430 697f849c-00de-4c27-9231-6c039bb93a67 Fri, 29 May 2020 00:15:00 -0700 Jupiter Broadcasting full Jupiter Broadcasting It's a storage showdown as Jim and Wes bust some performance myths about RAID and ZFS. 52:09 no It's a storage showdown as Jim and Wes bust some performance myths about RAID and ZFS. Plus our favorite features from Fedora 32, and why Wes loves DNF. DevOps, TechSNAP, Jupiter Broadcasting, A Cloud Guru, sysadmin podcast, Fedora, Fedora 32, Fedora Workstation, Ubuntu, Anaconda, Wayland, X11, Red Hat, CentOS, DNF, blivet, systemd, Linux, GNOME, Dash to Dock, Matthew Miller, LTS, rolling release, FUSE, OOM, EarlyOOM, ZFS, OpenZFS, DKMS, PPA, RAID, RAIDz, raid6, copy-on-write, vdev, storage, hard drive, SSD, HDD, spindle count, zpool, parity, filesystem, throughput, iops, chunk, block size, benchmarking It's a storage showdown as Jim and Wes bust some performance myths about RAID and ZFS.

Plus our favorite features from Fedora 32, and why Wes loves DNF.

Links:

]]> It's a storage showdown as Jim and Wes bust some performance myths about RAID and ZFS.

Plus our favorite features from Fedora 32, and why Wes loves DNF.

Links:

]]> 428: RAID Reality Check https://techsnap.systems/428 5556e3df-292d-4b0b-8e25-27f071862c06 Fri, 01 May 2020 00:15:00 -0700 Jupiter Broadcasting full Jupiter Broadcasting We dive deep into the world of RAID, and discuss how to choose the right topology to optimize performance and resilience. 36:00 no We dive deep into the world of RAID, and discuss how to choose the right topology to optimize performance and resilience. Plus Cloudflare steps up its campaign to secure BGP, and why you might want to trade in cron for systemd timers. DevOps, TechSNAP, Jupiter Broadcasting, A Cloud Guru, sysadmin podcast, EPYC, Threadripper, AMD, 7FX2, CPU, per-core performance, Intel, Threadripper, TDP, energy efficiency, RAID, md-raid, ZFS, hard disk performance, iops, hard drive, storage, Seagate, Iron Wolf, raidz, raidz2, RAID-5, RAID-6, RAID-10, ZFS, backups, fio, benchmarking, data integrity, BGP, Cloudflare, networking, RPKI, security, cryptography, route leak, routing, isbgpsafeyet, internet, systemd, systemd timers, cron, email, monitoring, We dive deep into the world of RAID, and discuss how to choose the right topology to optimize performance and resilience.

Plus Cloudflare steps up its campaign to secure BGP, and why you might want to trade in cron for systemd timers.

Links:

]]> We dive deep into the world of RAID, and discuss how to choose the right topology to optimize performance and resilience.

Plus Cloudflare steps up its campaign to secure BGP, and why you might want to trade in cron for systemd timers.

Links:

]]> 425: Ryzen Gets Real https://techsnap.systems/425 fc127e6a-cc96-408c-ae38-8049074a8f34 Fri, 20 Mar 2020 00:15:00 -0700 Jupiter Broadcasting full Jupiter Broadcasting We take a look at AMD's upcoming line of Ryzen 4000 mobile CPUs, and share our first impressions of Ubuntu 20.04's approach to ZFS on root. 32:53 no We take a look at AMD's upcoming line of Ryzen 4000 mobile CPUs, and share our first impressions of Ubuntu 20.04's approach to ZFS on root. Plus Let's Encrypt's certificate validation mix-up, Intel's questionable new power supply design, and more. Let's Encrypt, Boulder, Go, HTTPS, TLS, CAA, DNS, ACME, automation, Intel, AMD, Ryzen, Ryzen 4000, laptop, mobile processors, CPU, GPU, computer hardware, gaming, integrated graphics, graphics, battery life, Lenovo, Ryzen Mobile, ATX12VO, power supply, PSU, motherboard, electronics, iXsystems, TrueNAS, FreeNAS, TrueNAS Core, ZFS, fusion pools, storage, zsys, 20.04, Ubuntu, Canonical, snapshots, APT, sanoid, DevOps, TechSNAP, Jupiter Broadcasting, A Cloud Guru, Linux Academy, sysadmin podcast, We take a look at AMD's upcoming line of Ryzen 4000 mobile CPUs, and share our first impressions of Ubuntu 20.04's approach to ZFS on root.

Plus Let's Encrypt's certificate validation mix-up, Intel's questionable new power supply design, and more.

Links:

]]> We take a look at AMD's upcoming line of Ryzen 4000 mobile CPUs, and share our first impressions of Ubuntu 20.04's approach to ZFS on root.

Plus Let's Encrypt's certificate validation mix-up, Intel's questionable new power supply design, and more.

Links:

]]> 423: Hopeful for HAMR https://techsnap.systems/423 579b3028-f4b8-408a-ad04-ee0f8d017f78 Fri, 21 Feb 2020 18:00:00 -0800 Jupiter Broadcasting full Jupiter Broadcasting We explore the potential of heat-assisted magnetic recording and get excited about a possibly persistent L2ARC. 29:36 no We explore the potential of heat-assisted magnetic recording and get excited about a possibly persistent L2ARC. Plus Jim's journeys with Clear Linux, and why Ubuntu 18.04.4 is a maintenance release worth talking about. Ubuntu, 18.04.4, 18.04, LTS, Linux, WiFi, hardware enablement, maintenance release, Clear Linux OS, Linux desktop, Intel, Clear Linux, benchmarks, performance, swupd, ZFS, ZFS on Linux, ZoL, MobaXterm, LRU, WSL, Windows, Microsoft, L2ARC, ARC, filesystems, cache, caching, HDD, storage, hard drives, HAMR, SMR, MAMR, Seagate, Western Digital, latency, throughput, DevOps, TechSNAP, Jupiter Broadcasting, A Cloud Guru, Linux Academy, sysadmin podcast, We explore the potential of heat-assisted magnetic recording and get excited about a possibly persistent L2ARC.

Plus Jim's journeys with Clear Linux, and why Ubuntu 18.04.4 is a maintenance release worth talking about.

Links:

]]> We explore the potential of heat-assisted magnetic recording and get excited about a possibly persistent L2ARC.

Plus Jim's journeys with Clear Linux, and why Ubuntu 18.04.4 is a maintenance release worth talking about.

Links:

]]> 417: Machine Learning Magic https://techsnap.systems/417 88c620a6-0b1c-4698-aac4-ac757b632286 Fri, 29 Nov 2019 00:15:00 -0800 Jupiter Broadcasting full Jupiter Broadcasting We explore the rapid adoption of machine learning, its impact on computer architecture, and how to avoid AI snake oil. 26:27 no We explore the rapid adoption of machine learning, its impact on computer architecture, and how to avoid AI snake oil. Plus so-so SSD security, and a new wireless protocol that works best where the Wi-Fi sucks. OFNP,wireless,wifi,On-Off Noise Power Communication,LORA,WiFi 6,Ubiquiti ,Unifi,Amplifi,Amplifi Alien,mesh wifi,router,home networking,networking,wireless,ethernet,ASUS,AiMesh,OFDMA,Orthogonal Frequency-Division Multiple Access,SmallNetBuilder,Tim Higgins,SSD,storage,IEEE,encryption,cryptography,hardware encryption,BitLocker,LUKS,DBAN,hard disk,hard drive,storage,solid state,Secure Erase,ATA,security,machine learning,AI,artificial intelligence,artificial general intelligence,training,neural network,inference,drunkard's walk,Nvidia,Tesla V100,Matrix multiplication,linear algebra,supercomputers,NPU,TPU,Google,Jeffrey Dean,CPU,GPU,Chip Design,Deep Learning,Intel AVX512,Deep Learning Boost,OpenVINO,ResNet,i9-10980XE,Arvind Narayanan,AIExpert, DevOps, TechSNAP, Jupiter Broadcasting We explore the rapid adoption of machine learning, its impact on computer architecture, and how to avoid AI snake oil.

Plus so-so SSD security, and a new wireless protocol that works best where the Wi-Fi sucks.

Links:

]]> We explore the rapid adoption of machine learning, its impact on computer architecture, and how to avoid AI snake oil.

Plus so-so SSD security, and a new wireless protocol that works best where the Wi-Fi sucks.

Links:

]]> 405: Update Uncertainty https://techsnap.systems/405 8a576c94-20cc-497c-9de7-8402cd0a1135 Tue, 11 Jun 2019 20:15:00 -0700 Jupiter Broadcasting full Jupiter Broadcasting We explore the risky world of exposed RDP, from the brute force GoldBrute botnet to the dangerously worm-able BlueKeep vulnerability. 30:47 no We explore the risky world of exposed RDP, from the brute force GoldBrute botnet to the dangerously worm-able BlueKeep vulnerability. Plus the importance of automatic updates, and Jim's new backup box. BlueKeep, RDP, GoldBrute, Terminal Services, Remote Desktop, Windows, Windows Update, network security, security, firewalls, worm, internet worm, wannacry, NSA, Microsoft, updates, patching, vulnerabilities, automatic updates, backups, supermicro, rosewill, ssd, hard drive, NAS, storage, brute force, industrial control systems, out of support, windows xp, patching policies, password security, remote desktop protocol, DevOps, TechSNAP We explore the risky world of exposed RDP, from the brute force GoldBrute botnet to the dangerously worm-able BlueKeep vulnerability.

Plus the importance of automatic updates, and Jim's new backup box.

Links:

  • Errata Security: Almost One Million Vulnerable to BlueKeep Vuln (CVE-2019-0708) — Microsoft announced a vulnerability in it's "Remote Desktop" product that can lead to robust, wormable exploits. I scanned the Internet to assess the danger. I find nearly 1-million devices on the public Internet that are vulnerable to the bug.
  • Even the NSA is urging Windows users to patch BlueKeep (CVE-2019-0708) | ZDNet — "[The] NSA is concerned that malicious cyber actors will use the vulnerability in ransomware and exploit kits containing other known exploits, increasing capabilities against other unpatched systems.
  • Prevent a worm by updating Remote Desktop Services (CVE-2019-0708) – MSRC — This vulnerability is pre-authentication and requires no user interaction. In other words, the vulnerability is ‘wormable’, meaning that any future malware that exploits this vulnerability could propagate from vulnerable computer to vulnerable computer in a similar way as the WannaCry malware spread across the globe in 2017
  • BlueKeep - everyone agrees, you should patch PCs running legacy versions of Windows — I have this horrible feeling that the only way we’re going to wake the world up to the need to patch their ageing versions of Windows against the BlueKeep vulnerability is to wait until a malicious worm begins to spread around the world.
  • CVE-2019-0708 | Remote Desktop Services Remote Code Execution Vulnerability — A remote code execution vulnerability exists in Remote Desktop Services – formerly known as Terminal Services – when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests. This vulnerability is pre-authentication and requires no user interaction. An attacker who successfully exploited this vulnerability could execute arbitrary code on the target system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
  • Customer guidance for CVE-2019-0708 | Remote Desktop Services Remote Code Execution Vulnerability — Microsoft is aware that some customers are running versions of Windows that no longer receive mainstream support. That means those customers will not have received any security updates to protect their systems from CVE-2019-0708, which is a critical remote code execution vulnerability.
  • Forget BlueKeep: Beware the GoldBrute | Threatpost — In the past few days, GoldBrute (named after the Java class it uses) has attempted to brute-force Remote Desktop Protocol (RDP) connections for 1.5 million Windows systems and counting, according to Morphus Labs chief research officer Renato Marinho. The botnet is actively scanning the internet for machines with RDP exposed, and trying out weak or reused passwords to see if it can gain access to the systems.
  • The GoldBrute botnet — The latest round of bad news emerged last week when Morphus Labs’ researcher Renato Marinho announced the discovery of an aggressive brute force campaign against 1.5 million RDP servers by a botnet called ‘GoldBrute’.
  • Ubuntu Automatic Updates — The unattended-upgrades package can be used to automatically install updated packages, and can be configured to update all packages or just install security updates.
  • AutoUpdates - Fedora Project Wiki — You must decide whether to use automatic DNF or YUM updates on each of your machines.
  • It's time to block Windows Automatic Updating | Computerworld — Those of you who feel it’s important to install Windows and Office patches the moment they come out – I salute you. The Windows world needs more cannon fodder.
  • Windows 10's Ugly Updates Just Got Uglier. Here's How To Stay Safe by Disabling Automatic Updates — Stay safe by disabling automatic updates? How is that possible? As a general rule of thumb, I’d never recommend disabling updates because security patches are essential. But the situation with Windows 10 has become intolerable. Microsoft continues to fail and continues to release update after update that they know, or should know, has serious problems.
  • Jim's New Rig — I build, sell, and manage much bigger and meaner systems than this all the time. But this one's MINE! 12 hot swap bays, Ryzen 7 2700 w/ ECC RAM, quiet enough to share an office with, and the trays can take either HDD or SSD with no adapter needed.
]]> We explore the risky world of exposed RDP, from the brute force GoldBrute botnet to the dangerously worm-able BlueKeep vulnerability.

Plus the importance of automatic updates, and Jim's new backup box.

Links:

  • Errata Security: Almost One Million Vulnerable to BlueKeep Vuln (CVE-2019-0708) — Microsoft announced a vulnerability in it's "Remote Desktop" product that can lead to robust, wormable exploits. I scanned the Internet to assess the danger. I find nearly 1-million devices on the public Internet that are vulnerable to the bug.
  • Even the NSA is urging Windows users to patch BlueKeep (CVE-2019-0708) | ZDNet — "[The] NSA is concerned that malicious cyber actors will use the vulnerability in ransomware and exploit kits containing other known exploits, increasing capabilities against other unpatched systems.
  • Prevent a worm by updating Remote Desktop Services (CVE-2019-0708) – MSRC — This vulnerability is pre-authentication and requires no user interaction. In other words, the vulnerability is ‘wormable’, meaning that any future malware that exploits this vulnerability could propagate from vulnerable computer to vulnerable computer in a similar way as the WannaCry malware spread across the globe in 2017
  • BlueKeep - everyone agrees, you should patch PCs running legacy versions of Windows — I have this horrible feeling that the only way we’re going to wake the world up to the need to patch their ageing versions of Windows against the BlueKeep vulnerability is to wait until a malicious worm begins to spread around the world.
  • CVE-2019-0708 | Remote Desktop Services Remote Code Execution Vulnerability — A remote code execution vulnerability exists in Remote Desktop Services – formerly known as Terminal Services – when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests. This vulnerability is pre-authentication and requires no user interaction. An attacker who successfully exploited this vulnerability could execute arbitrary code on the target system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
  • Customer guidance for CVE-2019-0708 | Remote Desktop Services Remote Code Execution Vulnerability — Microsoft is aware that some customers are running versions of Windows that no longer receive mainstream support. That means those customers will not have received any security updates to protect their systems from CVE-2019-0708, which is a critical remote code execution vulnerability.
  • Forget BlueKeep: Beware the GoldBrute | Threatpost — In the past few days, GoldBrute (named after the Java class it uses) has attempted to brute-force Remote Desktop Protocol (RDP) connections for 1.5 million Windows systems and counting, according to Morphus Labs chief research officer Renato Marinho. The botnet is actively scanning the internet for machines with RDP exposed, and trying out weak or reused passwords to see if it can gain access to the systems.
  • The GoldBrute botnet — The latest round of bad news emerged last week when Morphus Labs’ researcher Renato Marinho announced the discovery of an aggressive brute force campaign against 1.5 million RDP servers by a botnet called ‘GoldBrute’.
  • Ubuntu Automatic Updates — The unattended-upgrades package can be used to automatically install updated packages, and can be configured to update all packages or just install security updates.
  • AutoUpdates - Fedora Project Wiki — You must decide whether to use automatic DNF or YUM updates on each of your machines.
  • It's time to block Windows Automatic Updating | Computerworld — Those of you who feel it’s important to install Windows and Office patches the moment they come out – I salute you. The Windows world needs more cannon fodder.
  • Windows 10's Ugly Updates Just Got Uglier. Here's How To Stay Safe by Disabling Automatic Updates — Stay safe by disabling automatic updates? How is that possible? As a general rule of thumb, I’d never recommend disabling updates because security patches are essential. But the situation with Windows 10 has become intolerable. Microsoft continues to fail and continues to release update after update that they know, or should know, has serious problems.
  • Jim's New Rig — I build, sell, and manage much bigger and meaner systems than this all the time. But this one's MINE! 12 hot swap bays, Ryzen 7 2700 w/ ECC RAM, quiet enough to share an office with, and the trays can take either HDD or SSD with no adapter needed.
]]> 396: Floating Point Problems https://techsnap.systems/396 bc968a3f-c804-4203-ae2b-dc43ef919218 Thu, 31 Jan 2019 20:45:00 -0800 Jupiter Broadcasting full Jupiter Broadcasting Jim and Wes are joined by OpenZFS developer Richard Yao to explain why the recent drama over Linux kernel 5.0 is no big deal, and how his fix for the underlying issue might actually make things faster. 27:11 no Jim and Wes are joined by OpenZFS developer Richard Yao to explain why the recent drama over Linux kernel 5.0 is no big deal, and how his fix for the underlying issue might actually make things faster. Plus the nitty-gritty details of vectorized optimizations and kernel preemption, and our thoughts on the future of the relationship between ZFS and Linux. Special Guest: Richard Yao. GPL, CDDL, Oracle, FPU, SIMD, vectorized instructions, AVX, hardware acceleration, journaling, data integrity, LFNW, floating point, checksum, snapshot, clone, FreeBSD, kernel module, header, software license, Linux, Multitasking, kernel preemption, OpenZFS, ZFS, ZoL, ZFS on Linux, Storage, RAID, ZVOL, SysAdmin podcast, DevOps, TechSNAP Jim and Wes are joined by OpenZFS developer Richard Yao to explain why the recent drama over Linux kernel 5.0 is no big deal, and how his fix for the underlying issue might actually make things faster.

Plus the nitty-gritty details of vectorized optimizations and kernel preemption, and our thoughts on the future of the relationship between ZFS and Linux.

Special Guest: Richard Yao.

Links:

  • LinuxFest Northwest 2019 — Join a bunch of JB hosts and community celebrating the 20th anniversary!
  • Choose Linux — The show that captures the excitement of discovering Linux.
  • Linux 5.0: _kernel_fpu{begin,end} no longer exported — The latest kernels removed the old compatibility headers.
  • ZFS On Linux Landing Workaround For Linux 5.0 Kernel Support — So while these symbols are important for SIMD vectorized checksums for ZFS in the name of performance, with Linux 5.0+ they are not going to be exported for use by non-GPL modules. ZFS On Linux developer Tony Hutter has now staged a change that would disable vector instructions on Linux 5.0+ kernels.
  • Re: x86/fpu: Don't export __kernel_fpu_{begin,end}() — My tolerance for ZFS is pretty non-existant. Sun explicitly did not want their code to work on Linux, so why would we do extra work to get their code to work properly?
  • The future of ZFS in FreeBSD — This state of affairs has led to a general agreement among the stakeholders that I have spoken to that it makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf has graciously encouraged me to add FreeBSD support directly so that we might all have a singleshared code base.
  • Dephix: Kickoff to The Future — OpenZFS has grown over the last decade, and delivering our application on Linux provides great OpenZFS support while enabling higher velocity adoption of new environments.
  • The future of ZFS on Linux [zfs-discuss] — Do you realize that we don’t actually need the symbols that the kernel removed. It All they do is save/restore of register state while turning off/on preemption. Nothing stops us from doing that ourselves. It is possible to implement our own substitutes using code from either Illumos or FreeBSD or even write our own. Honestly, I am beginning to think that my attempt to compromise with mainline gave the wrong impression. I am simply tired of this behavior by them and felt like reaching out to put an end to it. In a few weeks, we will likely be running on Linux 5.0 as if those symbols had never been removed because we will almost certainly have our own substitutes for them. Having to bloat our code because mainline won’t give us access to trivial functionality is annoying, but it is not the end of the world.
  • LINUX Unplugged Episode 284: Free as in Get Out
  • BSD Now 279: Future of ZFS
  • BSD Now 157: ZFS, The “Universal” File-system
]]> Jim and Wes are joined by OpenZFS developer Richard Yao to explain why the recent drama over Linux kernel 5.0 is no big deal, and how his fix for the underlying issue might actually make things faster.

Plus the nitty-gritty details of vectorized optimizations and kernel preemption, and our thoughts on the future of the relationship between ZFS and Linux.

Special Guest: Richard Yao.

Links:

  • LinuxFest Northwest 2019 — Join a bunch of JB hosts and community celebrating the 20th anniversary!
  • Choose Linux — The show that captures the excitement of discovering Linux.
  • Linux 5.0: _kernel_fpu{begin,end} no longer exported — The latest kernels removed the old compatibility headers.
  • ZFS On Linux Landing Workaround For Linux 5.0 Kernel Support — So while these symbols are important for SIMD vectorized checksums for ZFS in the name of performance, with Linux 5.0+ they are not going to be exported for use by non-GPL modules. ZFS On Linux developer Tony Hutter has now staged a change that would disable vector instructions on Linux 5.0+ kernels.
  • Re: x86/fpu: Don't export __kernel_fpu_{begin,end}() — My tolerance for ZFS is pretty non-existant. Sun explicitly did not want their code to work on Linux, so why would we do extra work to get their code to work properly?
  • The future of ZFS in FreeBSD — This state of affairs has led to a general agreement among the stakeholders that I have spoken to that it makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf has graciously encouraged me to add FreeBSD support directly so that we might all have a singleshared code base.
  • Dephix: Kickoff to The Future — OpenZFS has grown over the last decade, and delivering our application on Linux provides great OpenZFS support while enabling higher velocity adoption of new environments.
  • The future of ZFS on Linux [zfs-discuss] — Do you realize that we don’t actually need the symbols that the kernel removed. It All they do is save/restore of register state while turning off/on preemption. Nothing stops us from doing that ourselves. It is possible to implement our own substitutes using code from either Illumos or FreeBSD or even write our own. Honestly, I am beginning to think that my attempt to compromise with mainline gave the wrong impression. I am simply tired of this behavior by them and felt like reaching out to put an end to it. In a few weeks, we will likely be running on Linux 5.0 as if those symbols had never been removed because we will almost certainly have our own substitutes for them. Having to bloat our code because mainline won’t give us access to trivial functionality is annoying, but it is not the end of the world.
  • LINUX Unplugged Episode 284: Free as in Get Out
  • BSD Now 279: Future of ZFS
  • BSD Now 157: ZFS, The “Universal” File-system
]]> 392: Keeping up with Kubernetes https://techsnap.systems/392 45523a8f-70a8-4800-a757-964c8f91f645 Wed, 12 Dec 2018 19:00:00 -0800 Jupiter Broadcasting full Jupiter Broadcasting A security vulnerability in Kubernetes causes a big stir, but we’ll break it all down and explain what went wrong. 27:28 no A security vulnerability in Kubernetes causes a big stir, but we’ll break it all down and explain what went wrong. Plus the biggest stories out of Kubecon, and serverless gets serious. Kubecon, Kubernetes, Istio, CNCF, etcd, traefik, knative, google, k8s, red hat, ibm, openwhisk, serverless, faas, rook, cloud native, storage, ceph, Helm, Helm hub, Elasticsearch, Chromium OS, Chromium, Event driven, CloudEvent, Containers, Container Vulnerability, GitLab, Crossplane, Control Plane, Multicloud, holiday, christmas, security.christmas, CVE, Security Vulnerability, CVE-2018-1002105, kube-apiserver, websocket, RBAC, HTTP, metrics, Security, Networking, SysAdmin podcast, DevOps, TechSNAP A security vulnerability in Kubernetes causes a big stir, but we’ll break it all down and explain what went wrong.

Plus the biggest stories out of Kubecon, and serverless gets serious.

Links:

]]> A security vulnerability in Kubernetes causes a big stir, but we’ll break it all down and explain what went wrong.

Plus the biggest stories out of Kubecon, and serverless gets serious.

Links:

]]>