Podcasts about OpenShift

Fresh off Red Hat Summit, Chris is eyeing an exit from NixOS. What's luring him back to the mainstream? Our highlights, and the signal from the noise from open source's biggest event of the year.Sponsored By:Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices! 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Support LINUX UnpluggedLinks:

Send us a textIn this engaging episode, we dive into Dewan Ahmed's fascinating journey from electrical engineering to becoming a Principal Developer Advocate at Harness. Dewan shares how necessity drove his career transitions - first from renewable energy engineering to software development at IBM, and later to DevOps and Kubernetes. We explore the importance of content creation for career growth, how Toastmasters helped build his public speaking skills, and why job titles truly matter. Dewan also discusses his philosophy on resume reviews, having helped over 1,200 professionals pro bono, and shares insights on the delicate balance developer advocates must maintain between authenticity and company representation. Finally, we learn about his role organizing DevOps Days Halifax and his efforts to build the tech community in Atlantic Canada.Where to Find DewanLinkedIn: https://www.linkedin.com/in/diahmed/Twitter: https://x.com/dewanahmedBlog: https://www.dewanahmed.com/Company: https://www.harness.io/Show LinksToastmasters: https://www.toastmasters.org/DevOps Days Halifax: https://devopsdays.org/events/2024-halifax/welcome/Harness CI/CD: https://www.harness.io/products/continuous-integrationKubeCon: https://events.linuxfoundation.org/kubecon-cloudnativecon/OpenShift: https://www.redhat.com/en/technologies/cloud-computing/openshiftFollow, Like, and Subscribe!Podcast: https://www.thecloudgambit.com/YouTube: https://www.youtube.com/@TheCloudGambitLinkedIn: https://www.linkedin.com/company/thecloudgambitTwitter: https://twitter.com/TheCloudGambitTikTok: https://www.tiktok.com/@thecloudgambit

Welcome to episode 296 of The Cloud Pod – where the forecast is always cloudy! Today is a twofer – Justin and Ryan are in the house to make sure you don't miss out on any of today's important cloud and AI news. From AI Protection, to Google Next, to Amazon Q Developer, we've got it all, this week on TCP!  Titles we almost went with this week: Amazon Step Functions, walks step by step into my IDE Deepseek seeks the truth of “is it serverless or servers”?  Well Architected Reviews by AI… What will my solutions architects do now?  The cloud pod hosts steps over the Azure EU Data Boundary BYOIP to ALBs… only years too late for everyone. A big thanks to this week's sponsor: We're sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You've come to the right place! Send us an email or hit us up on our slack channel for more info.  General News  01:02 HashiCorp and Red Hat, better together  Hashicorp has more details on its future, with the recent IBM acquisition in this blog post.  They talk about the wide range of Day 2 operations, including things like drift detection, image management and patching, rightsizing, and configuration management.   As Red Hat Ansible is a purpose built operational management platform, it makes it easier to properly configure resources after the initial creation, but also to evolve the configuration after setup, and then execute ad-hoc playbooks to keep things running reliably and more securely at scale.  Some additional things they're exploring, now that the acquisition has closed: Red Hat Ansible Inventory generated dynamically by Terraform.  Official Terraform modules for Redhat Ansible, making it easier to trigger terraform from Ansible Playbooks. Redhat and Hashicorp officially support the Red Hat Ansible Provider for Terraform, making it easier to trigger Ansible from Terraform. Evolving Terraform provisioners to support a more comprehensive set of lifecycle integrations. Improved mechanisms to invoke Ansible Playbooks outside of the resource provisioning lifecycle Customers – not surprisingly – regularly integrate Vault and Openshift, and they have identified dozens of connection points that can add value, including: Vault Secrets Operator for OpenShift Etcd data encryption  Argo CI/CD Istio Certificate issuance 01:48 Justin – “That's a lot of promise for Ansible there, that I'm not sure it completely lives up to…” 07:09

Equilibrar modelos de inteligência artificial e aplicativos corporativos não é um jogo de soma zero. O futuro está em uma divisão bem equilibrada de modelos de IA e aplicativos tradicionais. Isso significa que os CIOs e as corporações têm um desafio: não só precisam planejar como integrar a IA em seus ambientes, mas também ter em mente como ela irá interagir com seus aplicativos existentes, passando por frentes que vão desde a segurança e a infraestrutura de sistemas até a composição das equipes e as habilidades necessárias. O podcast recebe Thiago Araki, diretor sênior de Tecnologia para a América Latina na Red Hat, e Bruno Machado, gerente sênior do OpenShift para a América Latina na Red Hat, para discutir como a combinação de IA e aplicativos irá evoluir, especialmente na medida em que os modelos se tornam mais especializados e as organizações vão além de tentar encontrar um único modelo de grande linguagem (LLM) para resolver todos os seus desafios. A apresentação é de Daniel Gonzales.See omnystudio.com/listener for privacy information.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 08/03 a 14/03.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 08/03 a 14/03.

 Deze aflevering is opgenomen tijdens de HCS Open Platform Experience 2024 in Amsterdam, waar we live in gesprek gingen over de nieuwste ontwikkelingen in Kubernetes en cloud-native technologieën. In deze aflevering van De Nederlandse Kubernetes Podcast duiken Ronald Kers (CNCF Ambassador) en Jan Stomphorst (Solutions Architect bij ACC ICT) samen met Wander Boessenkool (VP Training & Content Marketing bij HCS Company) in de wereld van GitOps, Kubernetes-clusterbeheer en AI.Wander heeft jarenlang ervaring als Red Hat-instructeur en deelt zijn kennis over hoe je GitOps niet alleen voor applicatiebeheer, maar ook voor je clusters zelf inzet. Hij legt uit waarom Customize vaak een betere keuze is dan Helm en hoe je met overlays en patches je Kubernetes-omgevingen flexibel en beheersbaar houdt.Daarnaast bespreken we hoe AI zich ontwikkelt binnen Kubernetes en OpenShift, en of AI-tools zoals Lightspeed daadwerkelijk het werk van een engineer kunnen verlichten of juist meer problemen veroorzaken. Ook nemen we een nostalgische duik in de IT-geschiedenis, van de Commodore 64 tot de nieuwste Kubernetes-oplossingen.Of je nu een Kubernetes-expert bent of net begint met GitOps, deze aflevering zit vol inzichten, handige tips en een flinke dosis tech-enthousiasme!

In deze aflevering van de Nederlandse Kubernetes Podcast spreken Ronald Kers (CNCF Ambassador) en Jan Stomphorst (Senior Solutions Architect bij ACC ICT) met Ruud Zwakenberg (Solution Architect bij Red Hat) tijdens de Red Hat Summit Connect 2024 in Nieuwegein.Ruud deelt zijn inzichten over AI-workloads op Kubernetes, de samenwerking tussen Red Hat en Intel, en hoe bedrijven slimmer en efficiënter AI-modellen kunnen trainen met OpenShift AI.Wat komt er aan bod?✅ De samenwerking tussen Red Hat en Intel: Hoe Intel's Gaudi-chipset helpt om AI-training te versnellen en OpenShift AI deze technologie optimaal benut.✅ AI-modellen trainen op Kubernetes: Waarom GPU's en gespecialiseerde AI-chips een must zijn en hoe OpenShift AI de compute power efficiënt verdeelt.✅ Duurzaamheid en AI: Hoe AI-training enorme hoeveelheden energie verbruikt en welke oplossingen er zijn om workloads efficiënter te draaien.✅ AI naar de Edge brengen: Waarom bedrijven steeds vaker AI-workloads dicht bij de gebruiker (Edge Computing) draaien en welke voordelen dit heeft.✅ De toekomst van Kubernetes & AI: Wat kunnen we verwachten op het gebied van schaalbaarheid, automatisering en energieverbruik in de komende jaren?Luister nu naar deze boeiende aflevering en ontdek hoe Red Hat en Intel samen werken aan de toekomst van AI op Kubernetes!

In this episode, we dive deeper into the new architectural trends for infrastructure designers in this coming decade, which is a transition from virtualization platforms first like VMware into containerized platforms first. But this time, we talk through the use of virtualization in containerized systems - keeping VMs but with what changes are necessary to make a containerized virtualization platform dominant instead of a virtualized virtualization platform. Reference: https://kubevirt.io/user-guide/architecture/ https://www.redhat.com/en/technologies/cloud-computing/openshift/virtualization

In today's episode of The Daily Windup, Eric Coffie interviews an expert who provides insights into the controls that need to be implemented by anybody using containers, such as OpenShift and Kubernetes. Organizations that modernize to the cloud and those running VMs may want to move to a more orchestrated environment using containers. They highlight the need for certain configurations, including agentless implementation and telemetry, for analysts to monitor environments for attacks, power abuses, and traffic. They also talk how FEMA helps organizations like the National Flood Insurance Program, move from a 5-year-old mainframe to OpenShift three, and soon to OpenShift four. The new technology allows for flood insurance to be issued in real-time, and they have set up an environment that can withstand external risks from the container platform while restricting access from the GetGo. Tune in to listen the importance of having these systems in place for your business!

In this episode of the Nederlandse Kubernetes Podcast, Ronald Kers (CNCF Ambassador) and Jan Stomphorst (Senior Solutions Architect bij ACC ICT) sit down with Wael Eldoamiry, Principal Solutions Architect at Red Hat, to discuss all things OpenShift, Kubernetes, and hybrid cloud.Wael takes us on a journey through the evolution of OpenShift, explaining how it builds on Kubernetes to provide a powerful, enterprise-ready container platform. He breaks down what's new in OpenShift 4.17, including:

Welcome to episode 276 of The Cloud Pod, where the forecast is always cloudy! This week, our hosts Justin, Matthew, and Jonathan do a speedrun of OpenWorld news, talk about energy needs and the totally not controversial decision to reopen 3 Mile Island, a “managed” exodus from cloud, and Kubernetes news. As well as Amazon’s RTO we are calling “Elastic Commute”. All this and more, right now on The Cloud Pod.  Titles we almost went with this week: The Cloud Pod Hosts don't own enough pants for five days a week IBM thinks it can contain the cost of K8s Microsoft loves nuclear energy The Cloudpod tries to give Oracle some love and still does not care The cloud pod goes nuclear on k8s costs Can IBM contain the costs of Kubernetes and Nuclear Power?  Google takes on take over while microsoft takes on nuclear AWS Launches ‘Managed Exodus’: Streamline Your Talent Drain Introducing Amazon WorkForce Alienation: Scale Your Employee Discontent to the Cloud Amazon SageMaker Studio Lab: Now with Real-Time Resignation Prediction A big thanks to this week's sponsor: We're sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You've come to the right place! Send us an email or hit us up on our slack channel for more info.  General News 01:08 IBM acquires Kubernetes cost optimization startup Kubecost  IBM is quickly becoming the place where cloud cost companies go to assimilate? Or Die? Rebirthed mabe? Either way, it's not a great place to end up.  On Tuesday they announced the acquisition of Kubecost, a FinOps startup that helps teams monitor and optimize their K8 clusters, with a focus on efficiency – and ultimately cost.  This acquisition follows the acquisitions of Apptio, Turbonomic, and Instana over the years.  Kubecost is the company behind OpenCost; a vendor-neutral open source project that forms part of the core Kubecost commercial offering.   OpenCost is part of the Cloud Native Computing Foundations cohort of sandbox projects. Kubecost is expected to be integrated into IBM’s FinOps Suite, which combines Cloudability and Turbonomic.  There is also speculation that it might make its way to OpenShift, too. 02:26 Jsutin- “…so KubeCost lives inside of Kubernetes, and basically has the ability to see how much CPU, how much memory they’re using, then calculate basically the price of the EC2 broken down into the different pods and services.” AI Is Going Great –

Ce mois-ci Yann nous parle de la disponibilité de NAbox pour de nouvelles plateformes de virtualisation ! Si votre hyperviseur est basé sur KVM ou Hyper-V, vous pouvez maintenant déployer NAbox !Worm et ARP sont maintenant inclus avec Cloud Volumes ONTAP sans coûts additionnels.VMware vCloud fondation est supporté avec NetAppTrident 24-06 supporte SnapMirror et les ONTAP Tools pour VMware supportent ActiveSync !Ne ratez pas les NetApp Insider's club et NetApp Insight Xtra !NFS supporte maintenant NFS-over-TLS et bien sûr on parle de NetApp Insight !Yann Bizeul (Linked-In)Guillaume Sowinski (Linked-In)Yves Weisser (Linked-In)

In this episode, guest host and AI correspondent Mofi Rahman interviews Richard Liaw and Kai-Hsun Chen from Anyscale about Ray and KubeRay. Ray is an open-source unified compute framework that makes it easy to scale AI and Python workloads, while KubeRay integrates Ray's capabilities into Kubernetes clusters.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod   News of the week CNCF Blog - LitmusChaos audit complete! Kubernetes Podcast from Google episode 234 - LitmusChaos, with Karthik Satchitanand Google Cloud Blog - Run your AI inference applications on Cloud Run with NVIDIA GPUs Diginomica article - KubeCon China - at 33-and-a-third, Linux is a long player. So, why does Linus Torvalds hate AI? CNCF-Hosted Co-Located Event Schedule for KubeCon NA 2024  Google Kubernetes Engine Release Notes - August 20, 2024 (1.31 available in Rapid Channel) Kubernetes Podcast from Google - Kubernetes v1.31: "Elli", with Angelos Kolaitis Red Hat Press Release - Red Hat OpenStack Services on OpenShift is Now Generally Available Red Hat Enables OpenStack to Run Natively on OpenShift Platform Broadcom Revamps Tanzu to Simplify Cloud-Native App Development and Deployment Tanzu Platform 10 Offers Cloud Foundry Users Deep Visibility and Productivity Enhancements VMware Explore Conference Website CNCF Blog - Announcing 500 Kubestronauts CNCF - Kubestronaut FAQ Dapr Day 2024 Virtual Event Website Links from the interview Kai-Hsun Chen on LinkedIn Richard Liaw on LinkedIn Ray from the RISE Lab at UC Berkeley Ray: A Distributed System for AI by Robert Nishihara and Philipp Moritz - Jan 9, 2018 KubeRay Docs KubeRay on GitHub PyTorch Apache Airflow Apache Spark Kubeflow Apache Submarine (retired) Jupyter Notebooks VS Code Examples of schedulers for Batch/AI workloads in Kubernetes Kueue Volcano Apache Yunikorn Examples of observability tools for Batch/AI workloads in Kubernetes Prometheus Grafana Fluentbit Examples of loadbalancers Nginx Istio Ray Data: Scalable Datasets for ML Dask Python - Parallel Python Ray Serve: Scalable and Programmable Serving HPA - Horizontal Pod Autoscaling in Kubernetes Karpenter - “Just-in-time nodes for any Kubernetes cluster” Lazy Computation Graphs with the Ray DAG API Types of hardware accelerators Google Cloud Tensor Processing Units (TPUs) AMD Instinct AMD Radeon AWS Trainium AWS Inferentia Pandas Numpy KubeCon EU 2024 - Accelerators(FPGA/GPU) Chaining to Efficiently Handle Large AI/ML Workloads in K8s - Sampath Priyankara, Nippon Telegraph and Telephone Corporation & Masataka Sonoda, Fujitsu Limited NVidia Megatron Links from the post-interview chat DRA - Dynamic Resource Allocation in Kubernetes Different ways of Running RayJob on Kubernetes Ray framework diagram in the docs  

Neste episódio temos uma conversa incrível que promete transformar a maneira como encaramos o feedback em nossos ambientes de trabalho. João Brito está no comando, e ele trouxe o André Brandão para abordar esse assunto tão crucial. Logo no início, ambos nos lembram que feedback não precisa ser um bicho de sete cabeças. André pode ser ouvido ressaltando: “Evitemos julgamentos, vamos focar no comportamento e não na pessoa!” Essa abordagem é fundamental para aliviar a tensão em situações que, muitas vezes, podem ser stressantes. O feedback deve ser uma ferramenta de crescimento, não um momento de desconforto.Uma das partes mais bacanas da conversa foi a troca de dicas práticas sobre como dar e receber feedback. André sugeriu que, quando formos fornecer feedback, precisamos ser sempre específicos. Ele afirma: “Quando você diz que alguém precisa melhorar, pergunte-se: em que exatamente?” Essa dica é valiosíssima, pois nos ajuda a evitar os comentários vagos que não levam a lugar nenhum e, muitas vezes, só adicionam confusão à situação.Outro momento de destaque foi quando falaram sobre a responsabilidade que cada um de nós deve ter no nosso próprio desenvolvimento. O André jogou a real ao afirmar: “Se não tomarmos as rédeas do nosso crescimento, quem vai?” Essa afirmação nos faz refletir que, para evoluir continuamente, precisamos reivindicar nosso espaço e nos esforçar ativamente.Para fechar, que tal aproveitarmos esses ensinamentos valiosos? Precisamos entrar nas nossas reuniões prontos para dar feedback de forma construtiva e também abrir espaço para receber críticas. A dica de André para criar um ambiente seguro durante essas interações é essencial: “Crie um ambiente seguro, onde as pessoas se sintam à vontade para compartilhar suas opiniões.”Nos vemos no próximo episódio!O Kubicast é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Os episódios do podcast estão nas principais plataformas de áudio digital e no YouTube.com/@getupcloud.

OpenShift is an open-source container application platform that brings Docker and Kubernetes together to help organizations build, deploy, and manage containerized applications. Open source OpenShift (OKD) powers some of the largest Kubernetes clusters, such as in CERN, the European Organization for Nuclear Research. Join us for a fireside chat with an OpenShift veteran Radek Vokál, on the current state of the OpenShift project, its vibrant community, and the pivotal role Red Hat plays in its development and growth. In this episode we delved into how observability is integrated within OpenShift, discussing key strategies, tools and open source projects for effective monitoring, troubleshooting and cost management. Whether you're managing complex deployments or seeking to enhance system performance, this episode offers valuable insights and practical guidance on leveraging OpenShift for improved observability. Don't miss this in-depth discussion! Our guest is Radek Vokál, Senior Manager, Red Hat Observability Product Management. With 20 years at Red Hat, Radek has been involved in OpenShift from engineering and product side. Radek currently leads product management for the OpenShift Observability. Radek has also been a co-organizer of the DevConf.cz open source community conference in the Czech Republic for the last 17 years. The episode was live-streamed on 8 August 2024 and the video is available at https://www.youtube.com/watch?v=oPNHJ7Nn8uA OpenObservability Talks episodes are released monthly, on the last Thursday of each month and are available for listening on your favorite podcast app and on YouTube. We live-stream the episodes on Twitch and YouTube Live - tune in to see us live, and chime in with your comments and questions on the live chat. ⁠⁠https://www.youtube.com/@openobservabilitytalks⁠   https://www.twitch.tv/openobservability⁠ Show Notes: 00:00 Episode and guest intro 06:29 What's OpenShift 10:22 OKD (OpenShift Core) open source 14:49 Product management for open source 19:27 Cost and resource efficiency of Kubernetes clusters 30:06 Observability at OpenShift 39:54 Open source observability stack used at OpenShift 42:12 Moving away from Grafana and adopting Perses OSS 45:04 OpenShift roadmap 48:40 Adopting OpenTelemetry 56:52 CrowdStrike and Azure outages 58:15 AWS taking down a suite of services 1:00:28 Jaeger V2 is coming 1:02:45 Episode outro Resources: https://okd.io/ https://www.redhat.com/observability https://github.com/korrel8r/korrel8r https://horovits.medium.com/033e7518eefb https://www.linkedin.com/feed/update/urn:li:share:7223575687339622400/ Socials: Twitter:⁠ https://twitter.com/OpenObserv⁠ YouTube: ⁠https://www.youtube.com/@openobservabilitytalks⁠ Dotan Horovits ============ Twitter: @horovits LinkedIn: www.linkedin.com/in/horovits Mastodon: @horovits@fosstodon Radek Vokál ========== Twitter: x.com/radekvokal  LInkedin: https://www.linkedin.com/in/radekvokal/  

Black Hat was last week and Hacker Summer Camp never fails to disappoint. There were some big takeaways from the show, such as Moxie Marlinspike telling DevOps they're the problem with security as well as a whole host of exploits, like the ones we've covered above. However, AI is king in 2024 and we knew everyone was going to be talking about it. Time Stamps: 0:00 - Welcome to The Rundown 1:13 - IBM Storage Scale using Blue Vela AI supercomputer 4:46 - AMD Chips Hit with Sinkclose 8:24 - BMC Uses AI For Mainframe Operations 12:38 - NIST Finalizes Post-Quantum Cryptography Standards 17:00 - RedHat's OpenShift Gets GenAI 20:32 - Pliops Kalray Merger Falls Through 23:14 - Announcements and Takeaways from Black Hat 23:48 - HPE Leverages AI for Security 28:18 - Copilot Insecure by Design 33:36 - More from Black Hat 38:20 - The Weeks Ahead 40:00 - Thanks for Watching Hosts: Tom Hollingsworth: https://www.twitter.com/NetworkingNerd Stephen Foskett: https://www.twitter.com/SFoskett Follow Gestalt IT Website: https://www.GestaltIT.com/ Twitter: https://www.twitter.com/GestaltIT LinkedIn: https://www.linkedin.com/company/Gestalt-IT Tags: #Rundown, #BlackHat2024, #Copilot, #AI, @IBM, @AMD, @BMCSoftware, @RedHat, @OpenShift, @Pliops, @Karlay, @HPE, @Microsoft, @NetworkingNerd, @SFoskett, @GestaltIT, @TheFuturumGroup, @TechstrongTV,

On this episode of DevOps Dialogues: Insights & Innovations, I am joined by Senior Director of Market Insights, Hybrid Platforms at Red Hat, Stuart Miniman, for a discussion on Red Hat Virtualization and AI Impacts on DevOps Our conversation covers: Highlights of Red Hat Summit Impacts of Virtualization and AI on the market Additions of Lightspeed into RHEL and OpenShift expanding on Ansible  

In this episode, we talk to three active leaders who have been around since the very beginning of Kubernetes. We explore how Kubernetes has changed since its inception, with a particular focus on current efforts in Open source Kubernetes to support AI/ML style workloads.   Maciej Szulik is currently taking a seat in the Kubernetes Steering Committee. He's also leading Special Interests Groups responsible for kubectl, workload and batch controllers. Maciej has been contributing to Kubernetes since the early days, jumping from one area to another where help was needed. He authored the first version of audit and helped shape its current one, as well as touched multiple other places in apimachinery. He was also responsible for designing and implementing Job and CronJob controllers. In kubectl he was responsible for the plugin mechanism and several major refactors to simplify the code. Since May 2024 he joined the ranks of Production Readiness Review (PRR) approvers helping ensure high production standards for the future of Kubernetes releases.    Clayton Coleman is a long-time Kubernetes contributor, having helped launch Kubernetes as open source, being on the bootstrap steering committee, and working across a number of SIGs to make Kubernetes a reliable and powerful foundation for workloads.  At Red Hat he led OpenShift's pivot onto Kubernetes and its growth across on-premise, edge, and into cloud.  At Google he is now focused on enabling the next generation of key workloads, especially AI/ML in Kubernetes and on GKE.   Dawn Chen has been a Principal Software Engineer at Google cloud since May 2007. Dawn has worked on an open source project called Kubernetes before the project was founded. She has been one of tech leads in both Kubernetes and GKE, and founded SIG Node from scratch. She also led Anthos platform team for the last 4 years, and mainly focuses on the core infrastructure. Prior to Kubernetes, she was the one of the tech leads for Google internal container infrastructure -- Borg for about 7 years. Outside of work, she is a wife, a mother of a 16-year old boy and a good friend. She enjoys reading, cooking, hiking and traveling.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod News of the week Kubernetes 1.31 Code Freeze is on July 9th Links from the interview Kubernetes Working Group Batch Kubernetes Working Group Serving Blog: Introducing Indexed Jobs (2021) Docs: Kubernetes Jobs KEP: Elastic Indexed Jobs Docs: Kubernetes CronJobs KubeCon EU 2021: The Long, Winding and Bumpy Road to CronJob's GA - Maciej Szulik, Red Hat & Alay Patel, Red Hat KubeCon EU 2018: Writing Kube Controllers for Everyone - Maciej Szulik, Red Hat (Beginner Skill Level) Kubernetes Working Group Device Management Kubernetes Enhancement Proposal process README DockerCon 2014: The announcement of Kubernetes at DockerCon Blog: AI & Kubernetes (by Kaslin) Kueue - “Kueue is a cloud-native job queueing system for batch, HPC, AI/ML, and similar applications in a Kubernetes cluster.” Whitepaper: Large-scale cluster management at {Google} with {Borg} Email: “Containers: Introduction” - An email introducing the concept of Linux containers to the Linux community Links from the post-interview chat Blog - “Scaling Kubernetes to 7,500 nodes” - OpenAI Ray on Kubernetes  

Ryan Wallner and Bhavin Shah talk to Andy Grimes about the OpenShift AI Landscape.Check out our website at https://kubernetesbytes.com/Episode Sponsor: Nethopper - Learn more about KAOPS: @nethopper.io - For a supported-demo: info@nethopper.io - Try the free version of KAOPS now! https://mynethopper.com/authLinks - https://youtube.com/watch?v=nAT9U1vJ8x0 - https://www.theregister.com/2024/06/12/kubertenes_decade_anniversary/ - https://www.businesswire.com/news/home/20240606882860/en/Mirantis-Collaboration-with-Pure-Storage-Simplifies-Data-Management-with-Kubernetes - https://falco.org/blog/falco-0-38-0/ - https://au.finance.yahoo.com/news/rancher-government-successfully-using-harvester-121100125.html - https://www.youtube.com/@PlatformEngineering - Video: https://www.youtube.com/watch?v=tZj8j3fdXy4 - Virtual Road Shows: https://www.redhat.com/en/north-america-red-hat-aws - AWS Gameday August 22nd: TBS - Boston Childrens Hospital RHOAI: https://www.redhat.com/en/creating-chris - IBM Open Source AI https://www.youtube.com/watch?v=SuGedexBudQ&t=141s

We look at OpenShift from an external perspective, including how it works in a multi-cloud environment, how it abstracts cloud resources, when administrators and developers still need to understand what is happening beneath the abstraction, combining OpenShift with cloud-managed services, some of the downsides of OpenShift, and where people should start if they want to... Read More

We look at OpenShift from an external perspective, including how it works in a multi-cloud environment, how it abstracts cloud resources, when administrators and developers still need to understand what is happening beneath the abstraction, combining OpenShift with cloud-managed services, some of the downsides of OpenShift, and where people should start if they want to … Continue reading "Hybrid Cloud Show – Episode 05"

Kubernetes is cool, and I think it's really useful in helping us scale and manage multiple systems easily in a fault-tolerant way. Actually, I don't think Kubernetes per se is important itself; more it seems that the idea of some orchestration engine to manage containers and systems is what really matters. As a side note, there are other orchestrators such as Mesos, OpenShift, and Nomad. However, do we need to know Kubernetes to use it for databases? This is a data platform newsletter, and most of us work with databases in some way. I do see more databases moving to the cloud, and a few moving to containers. I was thinking about this when I saw a Simple Talk article on Kubernetes for Complete Beginners. It's a basic article that looks at what the platform consists of, how it works, and how to set up a mini Kubernetes platform on your system. It's well written and interesting, but ... Read the rest of Kubernetes is Cool, But ...

Unlock the story behind IBM's bold play in acquiring HashiCorp, a move that's sent shockwaves through the tech sector. We pull back the curtain to reveal what this means for industry consolidation and how IBM's bet on HashiCorp's varied offerings, from Terraform to Vault, could be a game-changer for their private cloud ambitions. And with cloud giants like Google and Azure flaunting their latest earnings, we shed light on the true picture behind the numbers and the clever strategies they employ to stay ahead of the curve.Then, strap in as we examine Fortinet's pioneering move to infuse Gen AI into their FortiOS for unparalleled threat detection. We're not just observers; we're analysts questioning the practicality of Cisco and Red Hat's ACI and OpenShift integration and the unfolding saga within Cisco's own product ecosystem. Need a dose of reality? Our critique of the AWS Network Firewall, courtesy of insights from SDX Central, promises to mix humor with hard-hitting truths about cybersecurity in the cloud era. Join us for this episode that's anything but typical, as we navigate the intricate web of tech alliances and innovations.Check out the Fortnightly Cloud Networking NewsVisit our website and subscribe: https://www.cables2clouds.com/Follow us on Twitter: https://twitter.com/cables2cloudsFollow us on YouTube: https://www.youtube.com/@cables2clouds/Follow us on TikTok: https://www.tiktok.com/@cables2cloudsMerch Store: https://store.cables2clouds.com/Join the Discord Study group: https://artofneteng.com/iaatjArt of Network Engineering (AONE): https://artofnetworkengineering.com

Welcome to episode 251 of The Cloud Pod podcast – where the forecast is always cloudy! This week we're looking at the potential end of low impact code thanks to generative AI, how and why Kubernetes is still hanging on, and Cloudflare's new defensive AI project. Plus we take on the death of Project Titan in our aftershow.  Titles we almost went with this week: The Cloud Pod is Magic Why is the Cloud Pod Not on the Board of the Director for OpenAI The Cloud Pod wants Gen AI Money The Cloud Pod Thinks Magic Networks Are Less Fun Than Magic Mushrooms The Cloud Pod is Mission Critical so Give Us Your Money and Sponsor Us A big thanks to this week's sponsor: We're sponsorless this week! Interested in sponsoring us and having access to a specialized and targeted market? We'd love to talk to you. Send us an email or hit us up on our Slack Channel.  Follow-Up 00:50  Kubernetes Predictions Were Wrong — Redux Last week Ryan and Justin talked about why Kubernetes hasn't disappeared into the background during our after show, and now with Matt and Jonathan here I wanted to see if they had any additional thoughts.   If you missed this two weeks ago, it’s probably because you don't know that there are regular after shows after the final bumper of the show… typically about non-cloud things or things that generally interest our hosts. There is one today about the death of the Apple Car.  To summarize the conversation, ChatGPT has provided us with a sort of CliffsNotes version.  Ryan and Justin speculated on the reasons why Kubernetes (K8) persisted despite predictions of its decline: Global Pandemic Impact: They acknowledged the global pandemic that unfolded since 2020 and considered its potential influence on Kubernetes. The pandemic might have shifted priorities and accelerated digital transformation efforts, leading to increased reliance on Kubernetes for managing cloud-native applications and infrastructure. Organizations might have intensified their focus on scalable and resilient technologies like Kubernetes to adapt to remote work environments and changing market dynamics. Unforeseen Complexity: Despite expectations for a simpler alternative to emerge, Kubernetes has grown more complex over time. The ecosystem around Kubernetes has expanded significantly, with various platforms, services, and tools built on top of it. This complexity may have made it challenging for organizations to migrate away from Kubernetes, as they have heavily invested in its ecosystem and expertise. Critical Role in Scalability: Kubernetes remains a fundamental technology for platform engineering teams seeking to achieve scalability and standardization in their operations. Creating a standardized, opinionated path for Kubernetes within organizations enables them to streamline deployment processes, manage resources efficiently, and support the growing demands of modern applications. This critical role in scaling infrastructure and applications might have contributed to Kubernetes’ enduring relevance. Absence of Clear Alternatives: Despite predictions, no single service or platform has emerged as a clear, universally adopted alternative to Kubernetes. While other solutions exist, such as Tanzu, OpenShift, and others mentioned, none have achieved the same level of adoption or provided a compelling reason for orga

Now that businesses have deployed modern applications in the cloud they are starting to ask whether it might be more attractive to run these on-premises. This episode of the On-Premise IT podcast features Jason Benedicic, Camberley Bates, and Ian Sanderson discussing the pros and cons of cloud repatriation with Stephen Foskett. A recent blog post by 37 Signals got the Tech Field Day delegates talking about the reality of running modern applications in enterprise-owned clouds, whether in the datacenter or co-located. Certainly the hardware and software are available to move applications on-prem, and some workloads may be better served this way. Most of the necessary components to run modern web applications are available on-prem, from Kubernetes to Postgres to Kafka, but these can prove difficult to manage, which is one of the things as-a-service customers are paying for. Looking back to the debut of OpenStack, enterprises have wanted to run applications in-house but they found it too difficult to manage. OpenShift is much more attractive thanks to the support and integration of the platform, but many customers have financial and administrative reasons for as-a-service deployment. It might not be a mass exodus, but there are plenty of examples of repatriation of modern applications. © Gestalt IT, LLC for Gestalt IT: Cloud Repatriation is Really Happening

Now that businesses have deployed modern applications in the cloud they are starting to ask whether it might be more attractive to run these on-premises. This episode of the On-Premise IT podcast features Jason Benedicic, Camberley Bates, and Ian Sanderson discussing the pros and cons of cloud repatriation with Stephen Foskett. A recent blog post by 37 Signals got the Tech Field Day delegates talking about the reality of running modern applications in enterprise-owned clouds, whether in the datacenter or co-located. Certainly the hardware and software are available to move applications on-prem, and some workloads may be better served this way. Most of the necessary components to run modern web applications are available on-prem, from Kubernetes to Postgres to Kafka, but these can prove difficult to manage, which is one of the things as-a-service customers are paying for. Looking back to the debut of OpenStack, enterprises have wanted to run applications in-house but they found it too difficult to manage. OpenShift is much more attractive thanks to the support and integration of the platform, but many customers have financial and administrative reasons for as-a-service deployment. It might not be a mass exodus, but there are plenty of examples of repatriation of modern applications. © Gestalt IT, LLC for Gestalt IT: Cloud Repatriation is Really Happening

Portability and ease of deployment are the driving forces behind Acorn, a Kubernetes management platform based on the DevOps concept to simplify the work of Ops and Devs.To discuss how this Open Source project was born and is being developed, Kubicast brings in Darren Shepherd and Shannon Williams, co-founders of Acorn and also creators of Rancher.O Kubicast é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Os episódios do podcast estão em getup.io/kubicast, nas principais plataformas de áudio digital e no YouTube.com/@getupcloud.

O Kubicast é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Os episódios do podcast estão em getup.io/kubicast, nas principais plataformas de áudio digital e no YouTube.com/@getupcloud.

Leading global tech analysts Patrick Moorhead (Moor Insights & Strategy) and Daniel Newman (Futurum Research) are front and center on The Six Five analyzing the tech industry's biggest news each and every week and also conducting interviews with tech industry "insiders" on a regular basis.    The Six Five represents six (6) handpicked topics that will be covered for five (5) minutes each.    Welcome to this week's edition of “The 6-5.” I'm Patrick Moorhead with Moor Insights & Strategy, co-host, joined by Daniel Newman with Futurum Research. On this week's show we will be talking:   GlobalFoundries Q3 Earnings https://twitter.com/danielnewmanUV/status/1722186242580959535 https://investors.gf.com/   Arm Q2 Earnings https://twitter.com/PatrickMoorhead/status/1722359864687571090 https://twitter.com/danielnewmanUV/status/1722365154254266685 https://www.cnbc.com/2023/11/08/arm-earnings-report-q2-2024.html   OpenAI Announcements https://twitter.com/PatrickMoorhead/status/1721722266273067366   IBM AI and Research Day https://twitter.com/PatrickMoorhead/status/1722703728891822533 https://twitter.com/PatrickMoorhead/status/1722630297064554981 https://twitter.com/PatrickMoorhead/status/1722625645803667496 https://twitter.com/PatrickMoorhead/status/1722619472501256679 https://twitter.com/danielnewmanUV/status/1722645843700752853 https://twitter.com/danielnewmanUV/status/1722618130856603762   VMWare / IBM / OpenShift https://news.vmware.com/releases/vmware-explore-2023-barcelona-ibm-watsonx-private-ai   Synopsys RISC-V IP https://news.synopsys.com/2023-11-07-Synopsys-Expands-Its-ARC-Processor-IP-Portfolio-with-New-RISC-V-Family https://www.synopsys.com/glossary/what-is-risc-v.html   Disclaimer: This show is for information and entertainment purposes only. While we will discuss publicly traded companies on this show. The contents of this show should not be taken as investment advice.

Welcome back to another exciting episode of Data Driven! In today's episode, we're diving into the world of artificial intelligence, as our very own Frank La Vigne takes us on a journey through his experiences at the OpenShift Commons gathering in Raleigh.From delivering a captivating demo to moderating a thought-provoking panel, Frank's agenda is packed with fascinating insights and surprises. Join us as we explore the power of open source AI, the importance of community-driven innovation, and why transparency is key in today's evolving landscape. So sit back, relax, and get ready to delve into the world of AI at OpenShift Commons Gathering. Let's get started!Show Notes[00:01:31] Newcomer excited for first OpenShift gathering to give demo, moderate panel, and interview attendees. Registration booth opening soon, located near Raleigh's main park and an IMAX.[00:04:34] Transparency, innovation, trust in OpenAI, Elon Musk's comments on openness and Red Hat's departure.[00:07:53] Excitement about hall track conversations, public vs private cloud, and upcoming discussions.

This week, we discuss measuring developer productivity, Unity licensing backlash, and some follow-up on Wireless Emergency Alerts. Plus, thoughts on coconuts. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=bQtDvRPqXFs) 436 (https://www.youtube.com/watch?v=bQtDvRPqXFs) Runner-up Titles One day an ice machine will run on RISC-V Mo Developers Mo Problems W3C my ass. That's almost an aggressive blue. Wait. Do I live in an office complex? You pay the same Quarantine Quarters Maybe I have too much mindlessness Out of my way Costco, I'm going direct. Candy Corn Have you tried a bubble-sort? Omerta for developers Understand what you're measuring, or you'll just get measurements. KCNA23VMWEO20 Just make the bed Rundown Developer Productivity McKinsey Developer Productivity Review (https://dannorth.net/mckinsey-review/) Even longer rebuttal (https://newsletter.pragmaticengineer.com/p/measuring-developer-productivity). The only people who don't like metrics are the people being measured, or, developer productivity metrics quicksand (https://newsletter.cote.io/p/the-only-people-who-dont-like-metrics) Reports Kubernetes at Scale: Challenges, Priorities, Adoption Patterns, and Solutions (https://tanzu.vmware.com/content/analyst-reports/kubernetes-at-scale) Announcing the 2023 State of DevOps Report (https://cloud.google.com/blog/products/devops-sre/announcing-the-2023-state-of-devops-report) John Riccitiello is out at Unity, effective immediately (https://www.theverge.com/2023/10/9/23910441/unity-ceo-president-john-riccitiello-out-retire) Wireless Emergency Alerts (WEA) (https://www.fcc.gov/consumers/guides/wireless-emergency-alerts-wea) Relevant to your Interests Why companies still want in-house data centres (https://www.economist.com/business/2023/10/05/why-companies-still-want-in-house-data-centres) Understanding the Cyber Resilience Act: What Everyone involved in Open Source Development Should Know (https://www.linuxfoundation.org/blog/understanding-the-cyber-resilience-act) PayPal faces new antitrust lawsuit claiming it unfairly stifles competition with Stripe, Shopify and more (https://techcrunch.com/2023/10/05/paypal-faces-new-antitrust-lawsuit-claiming-it-unfairly-stifles-competition-with-stripe-shopify-and-more/) DuckDB Labs puts limit on free support, rules out VC funding (https://www.theregister.com/2023/10/05/duckdb_labs_puts_limit_on_vc_funds/) Genetics firm 23andMe says user data stolen in credential stuffing attack (https://www.bleepingcomputer.com/news/security/genetics-firm-23andme-says-user-data-stolen-in-credential-stuffing-attack/) Hackers are selling the data of millions lifted from 23andMe's genetic database (https://www.theverge.com/2023/10/7/23907330/23andme-leak-hackers-selling-user-dna-data) Datadog stumbles as Bank of America downgrades, citing recent checks (https://seekingalpha.com/news/4019064-datadog-stumbles-bank-of-america-downgrades-recent-checks) IBM CEO in damage control mode after AI job loss comments (https://www.itpro.com/technology/artificial-intelligence/ibm-ceo-in-damage-control-mode-after-ai-job-loss-comments) Google announces new generative AI search capabilities for doctors (https://www.cnbc.com/2023/10/09/google-announces-new-generative-ai-search-capabilities-for-doctors-.html) Be an Open Source Absolutist! (https://twitter.com/ID_AA_Carmack/status/1711737838889242880) Google Cloud mitigated largest DDoS attack, peaking above 398 million rps (https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/) Nonsense Ice Is Not Necessary. So Why Do Hotels Provide It for Free? (https://slate.com/human-interest/2015/08/why-are-there-ice-machines-in-so-many-hotels.html) Listener Feedback Biogen hiring Senior Manager, Solution Architecture, Global Commercial and Medical IT (hybrid work) (https://jobs.smartrecruiters.com/Biogen/743999935046183-senior-manager-solution-architecture-global-commercial-and-medical-it-hybrid-work-) RedHat hiring Principal Product Marketing Manager, OpenShift in Remote (https://us-redhat.icims.com/jobs/100399/principal-product-marketing-manager%2c-openshift/job?mode=view&mobile=true&width=428&height=739&bga=true&needsRedirect=false&jan1offset=-300&jun1offset=-240) Conferences Oct 17th SpringOne Tour Online (free!) (https://springonetour.io/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming) - Coté talking about platform engineering. Oct 17th and 24th **talk series (yes, a “webinar”): Building a Path to Production: A Guide for Managers and Leaders in Platform Engineering (https://series.brighttalk.com/series/6011/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming). Coté's doing this. Nov 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor, Matt's there. Use this VMware discount code for 20% off: KCNA23VMWEO20. Nov 6-9, 2023 VMware Explore Barcelona (https://www.vmware.com/explore/eu.html), Coté's attending Nov 7–8, 2023 RISC-V Summit | Linux Foundation Events (https://events.linuxfoundation.org/riscv-summit/) Jan 29, 2024 to Feb 1, 2024 That Conference Texas (https://that.us/events/tx/2024/schedule/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: macOS Sonoma (https://www.apple.com/macos/sonoma/) Matt: HomeSeek (https://www.homeseekgame.com/) - post apocalyptic SimCity Coté: Menewood (https://www.goodreads.com/en/book/show/60784675), finally out! Over 700 subscribers for my newsletter - are you subscribed (https://newsletter.cote.io)?! Photo Credits Header (https://unsplash.com/photos/dFoOWRT97_0) Artwork (https://unsplash.com/photos/umixjcVd0Ws)

Welcome episode 228 of the Cloud Pod podcast - where the forecast is always cloudy! This week your hosts Justin, Jonathan, Matthew and Ryan are taking a look at Magic Quadrant, Gemini AI, and GraalOS - along with all the latest news from OCI, Google, AWS, and Azure.  Titles we almost went with this week: The CloudPod wonders if Anthropic's Santa Clause will bring us everything we want in an AI Bot. The Cloud Pod recommends protection to achieve Safer Google rides the gemini rocket to AI JPB The only Copilot I need Azure, is Booze GraalOS, or what we now call ‘the noise our CFO makes when he receives the Oracle audit bills' The hosts of the Cloud pod would like to understand how to properly pronounce GraalOS Is Oracle even on the magic quadrant for cloud? RedHat Puts lipstick on the pig and calls it OpenStack A big thanks to this week's sponsor: Foghorn Consulting provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

In this episode of Kubernetes Bytes, Bhavin Shah and Ryan Wallner interview Brian Chambers, Chief Architect at Chick-fil-A. Brian walks through some of the design decisions, challenges and architecture of how Chick-fil-A uses Kubernetes at the edge in their restaurants.Join the Kubernetes Bytes slack using: https://bit.ly/k8sbytesReady to shop better hydration, use "kubernetesbytes" to save 20% off anything you order.Try Nom Nom today, go to https://trynom.com/kubernetesbytes and get 50% off your first order plus free shipping. 01:05 Introduction 06:22 Cloud Native News 19:13 Interview with Madhuri 01:13:20 TakeawaysCloud Native News: K8s 1.28 https://kubernetes.io/blog/2023/08/15/kubernetes-v1-28-release/ SC assignment stable- https://kubernetes.io/blog/2023/08/15/kubernetes-v1-28-release/#automatic-retroactive-assignment-of-a-default-storageclass-graduates-to-stable Non graceful shutdown stable - https://kubernetes.io/blog/2023/08/15/kubernetes-v1-28-release/#generally-available-recovery-from-non-graceful-node-shutdown Ceph RBD and FS in tree deprecated Control plan and node supported version go from n-2 to n-3 Redhat Openstack services on OpenShift - https://www.redhat.com/en/blog/red-hat-openstack-services-openshift-next-generation-red-hat-openstack-platform Alcion 21 Million funding round: https://techcrunch.com/2023/09/19/alcion-which-provides-backup-and-security-services-to-enterprises-raises-21m/ Veeam was major funder: https://www.techtarget.com/searchdatabackup/news/366552363/Veeam-leads-funding-round-for-SaaS-backup-provider-Alcion Kubescape 3.0 - https://kubescape.io/blog/2023/09/19/introducing-kubescape-3/ GPU sharing on Amazon EKS with NVIDIA time-slicing and accelerated EC2 instances or MIG based sharing https://aws.amazon.com/blogs/containers/gpu-sharing-on-amazon-eks-with-nvidia-time-slicing-and-accelerated-ec2-instances https://aws.amazon.com/blogs/containers/maximizing-gpu-utilization-with-nvidias-multi-instance-gpu-mig-on-amazon-eks-running-more-pods-per-gpu-for-enhanced-performance/ Akuity launches Kargo - New Open Source project to automate declarative promotion of changes across multiple app environments - https://www.businesswire.com/news/home/20230918552920/en/Akuity-Launches-Kargo---a-New-Open-Source-Project-to-Automate-the-Declarative-Promotion-of-Changes-Across-Multiple-Application-Environments OpenTofu - Linux Foundations alternative to Terraform - loads of community support https://www.linuxfoundation.org/press/announcing-opentofu?hss_channel=lcp-208777 CFP already open for Paris!!!! https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/cfp/ Spectro Cloud funding round - last was Series B - so this should be series C, but doesnt say. No amount disclosed, no valuation change disclosed. https://www.businesswire.com/news/home/20230914570380/en/Spectro-Cloud-Announces-Qualcomm-Ventures-Investment-to-Accelerate-Edge-and-AI-Innovation-at-Scale?hss_channel=lcp-36114581

Implantar banco de dados em Kubernetes é desafiador, mas possível e cada vez mais comum. Trabalhando há mais de 17 anos com banco de dados, o Sebastian Webber, Senior Software Engineer na Timescale, vem ao Kubicast para contar como foi essa descoberta e como segue sua saga para convencer as pessoas de que “tem que usar banco de dados em Kubernetes!”.Nessa conversa, também falamos de casos de fracasso com banco de dados, operadores de banco para Kubernetes e como convencer na “linguagem do lucro” sobre a importância de investir em infra. Links do episódio:Supercomputer Fugaku: https://www.fujitsu.com/global/about/innovation/fugaku/Meetup com o Somatório: https://www.youtube.com/watch?v=aAiqLwAdYvQOperadores de banco pra K8s: https://github.com/zalando/postgres-operatorhttps://stackgres.io/https://github.com/CrunchyData/postgres-operatorRecomendações do programa:Person of Interest - série  Barbie - filme Oppenheimer - filmeO Kubicast é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Os episódios do podcast estão em getup.io/kubicast, nas principais plataformas de áudio digital e no YouTube.com/@getupcloud.

Guest Veethika Mishra Panelist Richard Littauer | Django Skorupa | Victory Brown Show Notes Hello and welcome to Sustain Open Source Design! The podcast where we talk about sustaining open source with design. Learn how we, as designers, interface with open source in a sustainable way, how we integrate into different communities, and how we as coders, work with other designers. In today's episode, we are joined by guest, Veethika Mishra, a Senior Product Designer at GitLab, who shares her career path, emphasizing her move from closed to open source design work. She shares valuable insights into the design process at GitLab, which involves continuous interaction between designers and product managers and active participation of the user community. We discuss the power of open source contributions, the importance of community engagement, and the challenges faced in integrating external designers. Go ahead and download this episode now to hear more! [00:02:37] Veethika discusses her career path and transition from a secretive and proprietary organization to open source companies like Red Hat and GitLab. [00:04:25] At Red Hat, Veethika was part of the team that worked on the landing page for the developer console of OpenShift, which she greatly enjoyed. However, she wanted more engagement with the open source community, leading her to GitLab. [00:06:10] Richard asks Veethika about any potential advantages of design in a closed source environment, and she responds that she doesn't miss anything from her time in such an environment and considers some practices within these companies as absurd. [00:08:03] Django asks Veethika to talk about her research experiences, and she explains that research in an open environment provides a more accessible and authentic dataset, which benefits the product design process. [00:11:15] We hear about Veethika's GitLab's experience and the continuous learning process to ensure valuable community contributions. [00:13:29] Richard asks about the user base and the number of designers at GitLab, which Veethika reveals they have 30 million+ users, four designers in the CI/CD UX, and possible over 30 designers across the company. [00:14:05] Discussing the integration of designer input within developer teams at GitLab, Veethika describes GitLab's publicly documented product development flow. [00:16:19] Victory questions the collaboration between volunteer and employed designers at GitLab, and Veethika explains that while most designers working on different problems are GitLab employees, there are contribution guidelines for UX. She also mentions GitLab's Pajamas Design System as a more accessible and familiar space for designers to make contributions. [00:20:12] Richard asks about handling the potential backlash from unpopular design decisions. Veethika responds that there's no guaranteed way to mitigate such reactions but mentions that engaging with the community has made her a better communicator and designer. [00:21:03] We hear about the types of design contributions GitLab encourages from the community as Veethika explains the flexibility in contributions to Pajamas, and she details the process of making contributions via the Web IDE on the Pajamas website. [00:22:46] Richard asks about the barriers to open source design roles and how to overcome them. Veethika shares her opinion that the main barrier is the lack of open source ethos within many organizations. [00:25:19] Django asks if the scenario has changed over the years regarding open source design roles and Veethika notes an improvement in designer participation in open source. [00:26:45] Veethika tells us her views on Penpot Fest. [00:27:32] Veethika shares her hopes for the future of open source design, emphasizing the need for a deeper understanding of the socio-political impact of technological decisions and the diversification of the open source community. [00:29:21] Find out where you can follow Veethika and her work on the web. Quotes [00:10:17] “When you combine open and when you make it more visible and discoverable for others to see, these two things combined make a lot of impact.” [00:23:06] “If an organization isn't practicing open source development methods, then they have no reason having a designer that really cares for open source.” [00:23:16] “It's only when they live this ethos of openness when they realize the scale of impact this can bring to their business, not just to the community.” [00:24:51] “We can keep pointing fingers at others and not realize that it's also us who have a certain obligation towards the society and it's larger good, and open source is the only way to make it happen at this point.” [00:27:04] “Penpot Fest was really different!” [00:28:39] “We need to diversify the community that's behind open source projects.” Spotlight [00:30:07] Django's spotlight is Rory Colgan. [00:32:09] Victory's spotlight is CHAOSS Africa. [00:33:17] Richard's spotlight is LEUCHTTURM 1917 Journals. [00:33:53] Veethika's spotlight is Creative Commons. Links Open Source Design Twitter (https://twitter.com/opensrcdesign) Open Source Design (https://opensourcedesign.net/) Sustain Design & UX working group (https://discourse.sustainoss.org/t/design-ux-working-group/348) SustainOSS Discourse (https://discourse.sustainoss.org/) Sustain Open Source Twitter (https://twitter.com/sustainoss?lang=en) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Django Skorupa Twitter (https://twitter.com/djangoskorupa) Victory Brown Twitter (https://twitter.com/VictoryBrown_) Veethika Mishra Website (https://www.veethika.com/) Veethika Mishra GitLab (https://gitlab.com/veethika) Veethika Mishra LinkedIn (https://ca.linkedin.com/in/veethika?challengeId=AQE0QFpZIJctVwAAAYnB_ebDQoBVgurdSArdJwcVAPi22tNAdclHymNg3Bgyceb6HD6-dDQMDLONiOuud-komQ0u2t6haJsmYw&submissionId=2e2d1b66-5444-7817-de98-664e99d7a641&challengeSource=AgHO5PSHyIVaJAAAAYnB_huTH72Jq9WCHcvgrEiXolqg4DwUgX2zXchEpmBUbsE&challegeType=AgGx_trrGLUR3gAAAYnB_huXxh8Og4mNfaY5U7u0XqQDNXwd3MkqHxo&memberId=AgHreQY4Diu3tAAAAYnB_hubsoWMuJaLJ_yfhHZ2yNqOV-U&recognizeDevice=AgGY_DTeSInElwAAAYnB_hufpmtm6-hwSr-xE5QHgbrQljycKDrD) Veethika Mishra Mastodon (https://mastodon.social/@veethika) GitLab (https://about.gitlab.com/) Pajamas-GitLab Design System (https://design.gitlab.com/) Rory Colgan LinkedIn (https://de.linkedin.com/in/rorycolgan?original_referer=https%3A%2F%2Fwww.google.com%2F) CHAOSS Africa (https://github.com/chaoss/Chaoss-Africa) LEUCHTTURM 1917 Journals (https://www.leuchtturm1917.us/notebooks/journals/) Creative Commons (https://creativecommons.org/) Creative Commons Global Network (https://network.creativecommons.org/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Veethika Mishra.

Esse episódio do Kubicast traz uma conversa “muito fixe” com Ricardo Castro, o mago do CI/CD, que nos fala diretamente de Portugal, e também é Principal Engineer (SRE) na FanDuel e CDF Ambassador na CNCF.CI/CD é uma filosofia e não um conjunto de ferramentas. É possível fazer CI/CD de uma maneira certa com Jenkins e errada com Argo CD. Também, fazer CI/CD sem automação não é escalável, mas é possível.Falar de CI/CD parece um tema antigo, mas vale a pena conferir o papo, porque talvez o seu GitHub Actions não seja tudo o que o seu CI/CD poderia ou deveria fazer por você!Link do episódio:Kubicast #121 - Platform Engineering com a Natura https://www.getup.io/blog/kubicast-121-platform-engineering-na-real-com-natura/Recomendações do programa:A melhor forma de quebrar silos entre equipes é se comunicar! Queira saber o que fazem as outras pessoas da sua empresaSeja empático!Faça reuniões abertas e informais para participação de quem se interessarTenha interesse pelo negócio e não apenas pela parte técnica!O Kubicast é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Os episódios do podcast estão em getup.io/kubicast, nas principais plataformas de áudio digital e no YouTube.com/@getupcloud.

No episódio #128 do Kubicast, conversamos com Flávio Pimenta, Solutions Architect na Sensidea e palestrante dedicado à comunidade Cloud Native. O convidado compartilha sua incrível trajetória com a comunidade DevOps e enfatiza a importância dos feedbacks da comunidade para seu crescimento e aprimoramento. Flávio também se tornou um pilar na comunidade AWS, sendo reconhecido como referência na área. Não perca esse episódio inspirador para os interessados em Cloud Native e DevOps.

In this vignette of The 5G Factor, Ron Westfall and Steve Dickens provide their perspective on Red Hat becoming the primary infrastructure platform for Nokia's Core Network Applications. The conversation focused on: Red Hat Becomes the Primary Infrastructure Platform for Nokia's Core Network Applications. Nokia and Red Hat reached an agreement to integrate Nokia's core network applications with Red Hat OpenStack Platform and RedHat OpenShift. 350 personnel at Nokia will be transferring to Red Hat as Nokia moves on from developing the platforms that host its software. The duo will jointly support and evolve existing Nokia Container Services (NCS) and Nokia CloudBand Infrastructure Software (CBIS) customers while developing a path for customers to migrate to Red Hat's platforms. We delve into the implications for the 5G ecosystem and telco cloud journeys.

An airhacks.fm conversation with James Falkner (@schtool) about: TRS 80, TI-99/4A, enjoying assembly, starting at Solaris QA department, switching to Java Enterprise System (JES) group, working at liferay, starting at RedHat, becoming a Technical Product Marketing Manager at Red Hat, the ideal Java stack at RedHat, RHEL, ansible, quarkus, Watson X, ChatGPT is like an Autopilot in a car, Event-Driven Ansible, keycloak, prometheus, PostgreSQL, strimzi, Open Cluster Management, securing openshift clusters with StackRox, jenkins vs. ansible, OpenShift Pipelines with tekton, JBoss EAP on Azure, JBoss EAP on Azure App Service, business metrics on Azure, software updates on Azure App Service James Falkner on twitter: @schtool

As AI begins to go mainstream in IT, we're now at the stage where projects will either be AI-enabled or not, creating the new Bi-Modal IT for the 2020s.  SHOW: 722CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Find "Breaking Analysis Podcast with Dave Vellante" on Apple, Google and SpotifyKeep up to data with Enterprise Tech with theCUBESHOW NOTES:Why Digital Business needs BiModal IT (Gartner 2015)Slack getting an AI ChatbotNVIDIA shares spike on demand for AI chipsAI announcements from Microsoft Build 2023Windows and the AI Platform ShiftGoogle I/O and the coming AI BattlesRed Hat extends OpenShift for the Generative AI eraStackOverflow usage is down since ChatGPT launchEVERY VENDOR NOW HAS A PATH TO AI-INTEGRATED CAPABILITIESWhen cloud emerged in 2010s, IT projects became Bi-Modal (technology & people)Projects become classified as fast vs slow, old vs newGroups  become classified as fast vs slow, old vs newWILL AI-ENABLED CAPABILITIES CHANGE HOW AI PROJECTS ARE MEASURED?Expect AI to be asked about for every IT project, by leadershipExpect to see AI being pushed into every IT projectEvery vendor is going to highlight the AI integrations in their productsStart learning how the economics change if IT is potentially part of a projectExpect people-reduction to be a real consideration with AI projectsFEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

In this episode of Kubernetes Bytes, Ryan and Bhavin sit down with Sachin Mullick and Peter Lauterbach - the Product Management team at Red Hat focused on Red Hat OpenShift Virtualization and the open-source KubeVirt project and talk about how users can run containers and virtual machines side-by-side on the same Kubernetes cluster. They discuss the benefits of having a unified control plane for all your applications and the different features that enable users to run their applications in production. They also talk about some customers that have implemented this technology in production. Listen to learn more about how you can get started with KubeVirt and run your VMs alongside your Kubernetes pods on your Kubernetes or OpenShift clusters. 03:27 - News Segment 13:54 - KubeVirt Interview 01:06:12 - TakeawaysThe Motley Fool: Save $110 off the full list price of Stock Advisor for your first year, go to http://www.fool.com/kubernetesbytes and start your investing journey today! *$110 discount off of $199 per year list price. Membership will renew annually at the then current list pricShow Notes: 1. Kube by Example - https://kubebyexample.com/ 2. Ask An OpenShift Admin - https://youtube.com/playlist?list=PLaR6Rq6Z4IqdsG6b09q4QIv_Yq5fNL7zh 3. https://kubevirt.io/ 4. https://www.redhat.com/en/technologies/cloud-computing/openshift/virtualization Cloud-Native News: 1. New Security Startup - Stacklok - https://techcrunch.com/2023/05/17/kubernetes-and-sigstore-founders-raise-17-5m-to-launch-software-supply-chain-startup-stacklok/ 2. Traefik Lab announces Traefik Hub - Also raised $11M https://techcrunch.com/2023/05/17/traefik-labs-launches-traefik-hub-a-kubernetes-native-api-management-service/ 3. KSOC releases the KBOM standard - https://tech.einnews.com/pr_news/629861155/ksoc-releases-the-first-kubernetes-bill-of-materials-kbom-standard 4. Upbound announces managed Crossplane service - https://www.infoq.com/news/2023/05/upbound-managed-control-plane/ 5. Kubernetes 1.27 StatefulSet auto deletion for PVCs to beta https://kubernetes.io/blog/2023/05/04/kubernetes-1-27-statefulset-pvc-auto-deletion-beta/ 6. Cost reduction CAST AI company focuses on reducing compute costs running generative AI models on k8s https://siliconangle.com/2023/05/18/kubernetes-firm-cast-ai-adds-support-reducing-generative-ai-deployment-costs/ 7. Vault secret store operator https://thenewstack.io/hashicorp-vault-operator-manages-kubernetes-secrets/ 8. Managed Kafka or Run it yourself ? https://thenewstack.io/kafka-on-kubernetes-should-you-adopt-a-managed-solution/ 9. Cool usecase - edge k8s - robots picking fruit - https://thenewstack.io/fruit-picking-robots-powered-by-kubernetes-on-the-edge/ 10. Knative 1.10 release https://knative.dev/blog/releases/announcing-knative-v1-10-release/ (4-25 missed it)

In this sponsored podcast. The CTO Advisor, Keith Townsend, sits down with Roger Premo, General Manager, Corporate Strategy and Ventures, IBM. The duo discusses IBM's special relationship with Red Hat and how the company leverages OpenShift across public clouds, private infrastructure, and IBM's in-house products and services.

Sponsors Bitwarden (https://bitwarden.com/tux) Linode (https://linode.com/tux) - Application of the month n8n (https://n8n.io) Support TuxDigital and the Sudo Show Patreon (https://www.patreon.com/tuxdigital) Show Notes xCat (https://xcat.org) MaaS (https://maas.io) Uyuni (https://www.uyuni-project.org/) The Foreman (https://theforeman.org/) Cobbler (https://cobbler.github.io/) BiFrost - Standalone Ironic (https://docs.openstack.org/bifrost/latest/) TinkerBell (https://tinkerbell.org/) MetalKubed (https://metal3.io/) OpenStack (https://openstack.org) OpenShift (https://openshift.com) OKD - Upstream for OpenShift (https://okd.io) Kubernetes (https://kubernetes.io) Rancher (https://rancher.com) Harvester (https://harvesterhci.io/) Mist.io (https://mist.io) ManageIQ (https://manageiq.org) oVirt (https://ovirt.org) Interact with the hosts and the community https://tuxdigital.com/community/

About KelseyKelsey Hightower is the Principal Developer Advocate at Google, the co-chair of KubeCon, the world's premier Kubernetes conference, and an open source enthusiast. He's also the co-author of Kubernetes Up & Running: Dive into the Future of Infrastructure.Links: Twitter: @kelseyhightower Company site: Google.com Book: Kubernetes Up & Running: Dive into the Future of Infrastructure TranscriptAnnouncer: Hello and welcome to Screaming in the Cloud, with your host Cloud economist Corey Quinn. This weekly show features conversations with people doing interesting work in the world of Cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. I'm joined this week by Kelsey Hightower, who claims to be a principal developer advocate at Google, but based upon various keynotes I've seen him in, he basically gets on stage and plays video games like Tetris in front of large audiences. So I assume he is somehow involved with e-sports. Kelsey, welcome to the show.Kelsey: You've outed me. Most people didn't know that I am a full-time e-sports Tetris champion at home. And the technology thing is just a side gig.Corey: Exactly. It's one of those things you do just to keep the lights on, like you're waiting to get discovered, but in the meantime, you're waiting table. Same type of thing. Some people wait tables you more or less a sling Kubernetes, for lack of a better term.Kelsey: Yes.Corey: So let's dive right into this. You've been a strong proponent for a long time of Kubernetes and all of its intricacies and all the power that it unlocks and I've been pretty much the exact opposite of that, as far as saying it tends to be over complicated, that it's hype-driven and a whole bunch of other, shall we say criticisms that are sometimes bounded in reality and sometimes just because I think it'll be funny when I put them on Twitter. Where do you stand on the state of Kubernetes in 2020?Kelsey: So, I want to make sure it's clear what I do. Because when I started talking about Kubernetes, I was not working at Google. I was actually working at CoreOS where we had a competitor Kubernetes called Fleet. And Kubernetes coming out kind of put this like fork in our roadmap, like where do we go from here? What people saw me doing with Kubernetes was basically learning in public. Like I was really excited about the technology because it's attempting to solve a very complex thing. I think most people will agree building a distributed system is what cloud providers typically do, right? With VMs and hypervisors. Those are very big, complex distributed systems. And before Kubernetes came out, the closest I'd gotten to a distributed system before working at CoreOS was just reading the various white papers on the subject and hearing stories about how Google has systems like Borg tools, like Mesa was being used by some of the largest hyperscalers in the world, but I was never going to have the chance to ever touch one of those unless I would go work at one of those companies.So when Kubernetes came out and the fact that it was open source and I could read the code to understand how it was implemented, to understand how schedulers actually work and then bonus points for being able to contribute to it. Those early years, what you saw me doing was just being so excited about systems that I attended to build on my own, becoming this new thing just like Linux came up. So I kind of agree with you that a lot of people look at it as a more of a hype thing. They're looking at it regardless of their own needs, regardless of understanding how it works and what problems is trying to solve that. My stance on it, it's a really, really cool tool for the level that it operates in, and in order for it to be successful, people can't know that it's there.Corey: And I think that might be where part of my disconnect from Kubernetes comes into play. I have a background in ops, more or less, the grumpy Unix sysadmin because it's not like there's a second kind of Unix sysadmin you're ever going to encounter. Where everything in development works in theory, but in practice things pan out a little differently. I always joke that ops is the difference between theory and practice. In theory, devs can do everything and there's no ops needed. In practice, well it's been a burgeoning career for a while. The challenge with this is Kubernetes at times exposes certain levels of abstraction that, sorry certain levels of detail that generally people would not want to have to think about or deal with, while papering over other things with other layers of abstraction on top of it. That obscure, valuable troubleshooting information from a running something in an operational context. It absolutely is a fascinating piece of technology, but it feels today like it is overly complicated for the use a lot of people are attempting to put it to. Is that a fair criticism from where you sit?Kelsey: So I think the reason why it's a fair criticism is because there are people attempting to run their own Kubernetes cluster, right? So when we think about the cloud, unless you're in OpenStack land, but for the people who look at the cloud and you say, "Wow, this is much easier." There's an API for creating virtual machines and I don't see the distributed state store that's keeping all of that together. I don't see the farm of hypervisors. So we don't necessarily think about the inherent complexity into a system like that, because we just get to use it. So on one end, if you're just a user of a Kubernetes cluster, maybe using something fully managed or you have an ops team that's taking care of everything, your interface of the system becomes this Kubernetes configuration language where you say, "Give me a load balancer, give me three copies of this container running." And if we do it well, then you'd think it's a fairly easy system to deal with because you say, "kubectl, apply," and things seem to start running.Just like in the cloud where you say, "AWS create this VM, or G cloud compute instance, create." You just submit API calls and things happen. I think the fact that Kubernetes is very transparent to most people is, now you can see the complexity, right? Imagine everyone driving with the hood off the car. You'd be looking at a lot of moving things, but we have hoods on cars to hide the complexity and all we expose is the steering wheel and the pedals. That car is super complex but we don't see it. So therefore we don't attribute as complexity to the driving experience.Corey: This to some extent feels it's on the same axis as serverless, with just a different level of abstraction piled onto it. And while I am a large proponent of serverless, I think it's fantastic for a lot of Greenfield projects. The constraints inherent to the model mean that it is almost completely non-tenable for a tremendous number of existing workloads. Some developers like to call it legacy, but when I hear the term legacy I hear, "it makes actual money." So just treating it as, "Oh, it's a science experiment we can throw into a new environment, spend a bunch of time rewriting it for minimal gains," is just not going to happen as companies undergo digital transformations, if you'll pardon the term.Kelsey: Yeah, so I think you're right. So let's take Amazon's Lambda for example, it's a very opinionated high-level platform that assumes you're going to build apps a certain way. And if that's you, look, go for it. Now, one or two levels below that there is this distributed system. Kubernetes decided to play in that space because everyone that's building other platforms needs a place to start. The analogy I like to think of is like in the mobile space, iOS and Android deal with the complexities of managing multiple applications on a mobile device, security aspects, app stores, that kind of thing. And then you as a developer, you build your thing on top of those platforms and APIs and frameworks. Now, it's debatable, someone would say, "Why do we even need an open-source implementation of such a complex system? Why not just everyone moved to the cloud?" And then everyone that's not in a cloud on-premise gets left behind.But typically that's not how open source typically works, right? The reason why we have Linux, the precursor to the cloud is because someone looked at the big proprietary Unix systems and decided to re-implement them in a way that anyone could run those systems. So when you look at Kubernetes, you have to look at it from that lens. It's the ability to democratize these platform layers in a way that other people can innovate on top. That doesn't necessarily mean that everyone needs to start with Kubernetes, just like not everyone needs to start with the Linux server, but it's there for you to build the next thing on top of, if that's the route you want to go.Corey: It's been almost a year now since I made an original tweet about this, that in five years, no one will care about Kubernetes. So now I guess I have four years running on that clock and that attracted a bit of, shall we say controversy. There were people who thought that I meant that it was going to be a flash in the pan and it would dry up and blow away. But my impression of it is that in, well four years now, it will have become more or less system D for the data center, in that there's a bunch of complexity under the hood. It does a bunch of things. No-one sensible wants to spend all their time mucking around with it in most companies. But it's not something that people have to think about in an ongoing basis the way it feels like we do today.Kelsey: Yeah, I mean to me, I kind of see this as the natural evolution, right? It's new, it gets a lot of attention and kind of the assumption you make in that statement is there's something better that should be able to arise, giving that checkpoint. If this is what people think is hot, within five years surely we should see something else that can be deserving of that attention, right? Docker comes out and almost four or five years later you have Kubernetes. So it's obvious that there should be a progression here that steals some of the attention away from Kubernetes, but I think where it's so new, right? It's only five years in, Linux is like over 20 years old now at this point, and it's still top of mind for a lot of people, right? Microsoft is still porting a lot of Windows only things into Linux, so we still discuss the differences between Windows and Linux.The idea that the cloud, for the most part, is driven by Linux virtual machines, that I think the majority of workloads run on virtual machines still to this day, so it's still front and center, especially if you're a system administrator managing BDMs, right? You're dealing with tools that target Linux, you know the Cisco interface and you're thinking about how to secure it and lock it down. Kubernetes is just at the very first part of that life cycle where it's new. We're all interested in even what it is and how it works, and now we're starting to move into that next phase, which is the distro phase. Like in Linux, you had Red Hat, Slackware, Ubuntu, special purpose distros.Some will consider Android a special purpose distribution of Linux for mobile devices. And now that we're in this distro phase, that's going to go on for another 5 to 10 years where people start to align themselves around, maybe it's OpenShift, maybe it's GKE, maybe it's Fargate for EKS. These are now distributions built on top of Kubernetes that start to add a little bit more opinionation about how Kubernetes should be pushed together. And then we'll enter another phase where you'll build a platform on top of Kubernetes, but it won't be worth mentioning that Kubernetes is underneath because people will be more interested on the thing above.Corey: I think we're already seeing that now, in terms of people no longer really care that much what operating system they're running, let alone with distribution of that operating system. The things that you have to care about slip below the surface of awareness and we've seen this for a long time now. Originally to install a web server, it wound up taking a few days and an intimate knowledge of GCC compiler flags, then RPM or D package and then yum on top of that, then ensure installed, once we had configuration management that was halfway decent.Then Docker run, whatever it is. And today feels like it's with serverless technologies being what they are, it's effectively a push a file to S3 or it's equivalent somewhere else and you're done. The things that people have to be aware of and the barrier to entry continually lowers. The downside to that of course, is that things that people specialize in today and effectively make very lucrative careers out of are going to be not front and center in 5 to 10 years the way that they are today. And that's always been the way of technology. It's a treadmill to some extent.Kelsey: And on the flip side of that, look at all of the new jobs that are centered around these cloud-native technologies, right? So you know, we're just going to make up some numbers here, imagine if there were only 10,000 jobs around just Linux system administration. Now when you look at this whole Kubernetes landscape where people are saying we can actually do a better job with metrics and monitoring. Observability is now a thing culturally that people assume you should have, because you're dealing with these distributed systems. The ability to start thinking about multi-regional deployments when I think that would've been infeasible with the previous tools or you'd have to build all those tools yourself. So I think now we're starting to see a lot more opportunities, where instead of 10,000 people, maybe you need 20,000 people because now you have the tools necessary to tackle bigger projects where you didn't see that before.Corey: That's what's going to be really neat to see. But the challenge is always to people who are steeped in existing technologies. What does this mean for them? I mean I spent a lot of time early in my career fighting against cloud because I thought that it was taking away a cornerstone of my identity. I was a large scale Unix administrator, specifically focusing on email. Well, it turns out that there aren't nearly as many companies that need to have that particular skill set in house as it did 10 years ago. And what we're seeing now is this sort of forced evolution of people's skillsets or they hunker down on a particular area of technology or particular application to try and make a bet that they can ride that out until retirement. It's challenging, but at some point it seems that some folks like to stop learning, and I don't fully pretend to understand that. I'm sure I will someday where, "No, at this point technology come far enough. We're just going to stop here, and anything after this is garbage." I hope not, but I can see a world in which that happens.Kelsey: Yeah, and I also think one thing that we don't talk a lot about in the Kubernetes community, is that Kubernetes makes hyper-specialization worth doing because now you start to have a clear separation from concerns. Now the OS can be hyperfocused on security system calls and not necessarily packaging every programming language under the sun into a single distribution. So we can kind of move part of that layer out of the core OS and start to just think about the OS being a security boundary where we try to lock things down. And for some people that play at that layer, they have a lot of work ahead of them in locking down these system calls, improving the idea of containerization, whether that's something like Firecracker or some of the work that you see VMware doing, that's going to be a whole class of hyper-specialization. And the reason why they're going to be able to focus now is because we're starting to move into a world, whether that's serverless or the Kubernetes API.We're saying we should deploy applications that don't target machines. I mean just that step alone is going to allow for so much specialization at the various layers because even on the networking front, which arguably has been a specialization up until this point, can truly specialize because now the IP assignments, how networking fits together, has also abstracted a way one more step where you're not asking for interfaces or binding to a specific port or playing with port mappings. You can now let the platform do that. So I think for some of the people who may be not as interested as moving up the stack, they need to be aware that the number of people we need being hyper-specialized at Linux administration will definitely shrink. And a lot of that work will move up the stack, whether that's Kubernetes or managing a serverless deployment and all the configuration that goes with that. But if you are a Linux, like that is your bread and butter, I think there's going to be an opportunity to go super deep, but you may have to expand into things like security and not just things like configuration management.Corey: Let's call it the unfulfilled promise of Kubernetes. On paper, I love what it hints at being possible. Namely, if I build something that runs well on top of Kubernetes than we truly have a write once, run anywhere type of environment. Stop me if you've heard that one before, 50,000 times in our industry... or history. But in practice, as has happened before, it seems like it tends to fall down for one reason or another. Now, Amazon is famous because for many reasons, but the one that I like to pick on them for is, you can't say the word multi-cloud at their events. Right. That'll change people's perspective, good job. The people tend to see multi-cloud are a couple of different lenses.I've been rather anti multi-cloud from the perspective of the idea that you're setting out day one to build an application with the idea that it can be run on top of any cloud provider, or even on-premises if that's what you want to do, is generally not the way to proceed. You wind up having to make certain trade-offs along the way, you have to rebuild anything that isn't consistent between those providers, and it slows you down. Kubernetes on the other hand hints at if it works and fulfills this promise, you can suddenly abstract an awful lot beyond that and just write generic applications that can run anywhere. Where do you stand on the whole multi-cloud topic?Kelsey: So I think we have to make sure we talk about the different layers that are kind of ready for this thing. So for example, like multi-cloud networking, we just call that networking, right? What's the IP address over there? I can just hit it. So we don't make a big deal about multi-cloud networking. Now there's an area where people say, how do I configure the various cloud providers? And I think the healthy way to think about this is, in your own data centers, right, so we know a lot of people have investments on-premises. Now, if you were to take the mindset that you only need one provider, then you would try to buy everything from HP, right? You would buy HP store's devices, you buy HP racks, power. Maybe HP doesn't sell air conditioners. So you're going to have to buy an air conditioner from a vendor who specializes in making air conditioners, hopefully for a data center and not your house.So now you've entered this world where one vendor does it make every single piece that you need. Now in the data center, we don't say, "Oh, I am multi-vendor in my data center." Typically, you just buy the switches that you need, you buy the power racks that you need, you buy the ethernet cables that you need, and they have common interfaces that allow them to connect together and they typically have different configuration languages and methods for configuring those components. The cloud on the other hand also represents the same kind of opportunity. There are some people who really love DynamoDB and S3, but then they may prefer something like BigQuery to analyze the data that they're uploading into S3. Now, if this was a data center, you would just buy all three of those things and put them in the same rack and call it good.But the cloud presents this other challenge. How do you authenticate to those systems? And then there's usually this additional networking costs, egress or ingress charges that make it prohibitive to say, "I want to use two different products from two different vendors." And I think that's-Corey: ...winds up causing serious problems.Kelsey: Yes, so that data gravity, the associated cost becomes a little bit more in your face. Whereas, in a data center you kind of feel that the cost has already been paid. I already have a network switch with enough bandwidth, I have an extra port on my switch to plug this thing in and they're all standard interfaces. Why not? So I think the multi-cloud gets lost in the chew problem, which is the barrier to entry of leveraging things across two different providers because of networking and configuration practices.Corey: That's often the challenge, I think, that people get bogged down in. On an earlier episode of this show we had Mitchell Hashimoto on, and his entire theory around using Terraform to wind up configuring various bits of infrastructure, was not the idea of workload portability because that feels like the windmill we all keep tilting at and failing to hit. But instead the idea of workflow portability, where different things can wind up being interacted with in the same way. So if this one division is on one cloud provider, the others are on something else, then you at least can have some points of consistency in how you interact with those things. And in the event that you do need to move, you don't have to effectively redo all of your CICD process, all of your tooling, et cetera. And I thought that there was something compelling about that argument.Kelsey: And that's actually what Kubernetes does for a lot of people. For Kubernetes, if you think about it, when we start to talk about workflow consistency, if you want to deploy an application, queue CTL, apply, some config, you want the application to have a load balancer in front of it. Regardless of the cloud provider, because Kubernetes has an extension point we call the cloud provider. And that's where Amazon, Azure, Google Cloud, we do all the heavy lifting of mapping the high-level ingress object that specifies, "I want a load balancer, maybe a few options," to the actual implementation detail. So maybe you don't have to use four or five different tools and that's where that kind of workload portability comes from. Like if you think about Linux, right? It has a set of system calls, for the most part, even if you're using a different distro at this point, Red Hat or Amazon Linux or Google's container optimized Linux.If I build a Go binary on my laptop, I can SCP it to any of those Linux machines and it's going to probably run. So you could call that multi-cloud, but that doesn't make a lot of sense because it's just because of the way Linux works. Kubernetes does something very similar because it sits right on top of Linux, so you get the portability just from the previous example and then you get the other portability and workload, like you just stated, where I'm calling kubectl apply, and I'm using the same workflow to get resources spun up on the various cloud providers. Even if that configuration isn't one-to-one identical.Corey: This episode is sponsored in part by our friends at Uptycs, because they believe that many of you are looking to bolster your security posture with CNAPP and XDR solutions. They offer both cloud and endpoint security in a single UI and data model. Listeners can get Uptycs for up to 1,000 assets through the end of 2023 (that is next year) for $1. But this offer is only available for a limited time on UptycsSecretMenu.com. That's U-P-T-Y-C-S Secret Menu dot com.Corey: One thing I'm curious about is you wind up walking through the world and seeing companies adopting Kubernetes in different ways. How are you finding the adoption of Kubernetes is looking like inside of big E enterprise style companies? I don't have as much insight into those environments as I probably should. That's sort of a focus area for the next year for me. But in startups, it seems that it's either someone goes in and rolls it out and suddenly it's fantastic, or they avoid it entirely and do something serverless. In large enterprises, I see a lot of Kubernetes and a lot of Kubernetes stories coming out of it, but what isn't usually told is, what's the tipping point where they say, "Yeah, let's try this." Or, "Here's the problem we're trying to solve for. Let's chase it."Kelsey: What I see is enterprises buy everything. If you're big enough and you have a big enough IT budget, most enterprises have a POC of everything that's for sale, period. There's some team in some pocket, maybe they came through via acquisition. Maybe they live in a different state. Maybe it's just a new project that came out. And what you tend to see, at least from my experiences, if I walk into a typical enterprise, they may tell me something like, "Hey, we have a POC, a Pivotal Cloud Foundry, OpenShift, and we want some of that new thing that we just saw from you guys. How do we get a POC going?" So there's always this appetite to evaluate what's for sale, right? So, that's one case. There's another case where, when you start to think about an enterprise there's a big range of skillsets. Sometimes I'll go to some companies like, "Oh, my insurance is through that company, and there's ex-Googlers that work there." They used to work on things like Borg, or something else, and they kind of know how these systems work.And they have a slightly better edge at evaluating whether Kubernetes is any good for the problem at hand. And you'll see them bring it in. Now that same company, I could drive over to the other campus, maybe it's five miles away and that team doesn't even know what Kubernetes is. And for them, they're going to be chugging along with what they're currently doing. So then the challenge becomes if Kubernetes is a great fit, how wide of a fit it isn't? How many teams at that company should be using it? So what I'm currently seeing as there are some enterprises that have found a way to make Kubernetes the place where they do a lot of new work, because that makes sense. A lot of enterprises to my surprise though, are actually stepping back and saying, "You know what? We've been stitching together our own platform for the last five years. We had the Netflix stack, we got some Spring Boot, we got Console, we got Vault, we got Docker. And now this whole thing is getting a little more fragile because we're doing all of this glue code."Kubernetes, We've been trying to build our own Kubernetes and now that we know what it is and we know what it isn't, we know that we can probably get rid of this kind of bespoke stack ourselves and just because of the ecosystem, right? If I go to HashiCorp's website, I would probably find the word Kubernetes as much as I find the word Nomad on their site because they've made things like Console and Vault become first-class offerings inside of the world of Kubernetes. So I think it's that momentum that you see across even People Oracle, Juniper, Palo Alto Networks, they're all have seem to have a Kubernetes story. And this is why you start to see the enterprise able to adopt it because it's so much in their face and it's where the ecosystem is going.Corey: It feels like a lot of the excitement and the promise and even the same problems that Kubernetes is aimed at today, could have just as easily been talked about half a decade ago in the context of OpenStack. And for better or worse, OpenStack is nowhere near where it once was. It would felt like it had such promise and such potential and when it didn't pan out, that left a lot of people feeling relatively sad, burnt out, depressed, et cetera. And I'm seeing a lot of parallels today, at least between what was said about OpenStack and what was said about Kubernetes. How do you see those two diverging?Kelsey: I will tell you the big difference that I saw, personally. Just for my personal journey outside of Google, just having that option. And I remember I was working at a company and we were like, "We're going to roll our own OpenStack. We're going to buy a free BSD box and make it a file server. We're going all open sources," like do whatever you want to do. And that was just having so many issues in terms of first-class integrations, education, people with the skills to even do that. And I was like, "You know what, let's just cut the check for VMware." We want virtualization. VMware, for the cost and when it does, it's good enough. Or we can just actually use a cloud provider. That space in many ways was a purely solved problem. Now, let's fast forward to Kubernetes, and also when you get OpenStack finished, you're just back where you started.You got a bunch of VMs and now you've got to go figure out how to build the real platform that people want to use because no one just wants a VM. If you think Kubernetes is low level, just having OpenStack, even OpenStack was perfect. You're still at square one for the most part. Maybe you can just say, "Now I'm paying a little less money for my stack in terms of software licensing costs," but from an extraction and automation and API standpoint, I don't think OpenStack moved the needle in that regard. Now in the Kubernetes world, it's solving a huge gap.Lots of people have virtual machine sprawl than they had Docker sprawl, and when you bring in this thing by Kubernetes, it says, "You know what? Let's reign all of that in. Let's build some first-class abstractions, assuming that the layer below us is a solved problem." You got to remember when Kubernetes came out, it wasn't trying to replace the hypervisor, it assumed it was there. It also assumed that the hypervisor had APIs for creating virtual machines and attaching disc and creating load balancers, so Kubernetes came out as a complementary technology, not one looking to replace. And I think that's why it was able to stick because it solved a problem at another layer where there was not a lot of competition.Corey: I think a more cynical take, at least one of the ones that I've heard articulated and I tend to agree with, was that OpenStack originally seemed super awesome because there were a lot of interesting people behind it, fascinating organizations, but then you wound up looking through the backers of the foundation behind it and the rest. And there were something like 500 companies behind it, an awful lot of them were these giant organizations that ... they were big e-corporate IT enterprise software vendors, and you take a look at that, I'm not going to name anyone because at that point, oh will we get letters.But at that point, you start seeing so many of the patterns being worked into it that it almost feels like it has to collapse under its own weight. I don't, for better or worse, get the sense that Kubernetes is succumbing to the same thing, despite the CNCF having an awful lot of those same backers behind it and as far as I can tell, significantly more money, they seem to have all the money to throw at these sorts of things. So I'm wondering how Kubernetes has managed to effectively sidestep I guess the open-source miasma that OpenStack didn't quite manage to avoid.Kelsey: Kubernetes gained its own identity before the foundation existed. Its purpose, if you think back from the Borg paper almost eight years prior, maybe even 10 years prior. It defined this problem really, really well. I think Mesos came out and also had a slightly different take on this problem. And you could just see at that time there was a real need, you had choices between Docker Swarm, Nomad. It seems like everybody was trying to fill in this gap because, across most verticals or industries, this was a true problem worth solving. What Kubernetes did was played in the exact same sandbox, but it kind of got put out with experience. It's not like, "Oh, let's just copy this thing that already exists, but let's just make it open."And in that case, you don't really have your own identity. It's you versus Amazon, in the case of OpenStack, it's you versus VMware. And that's just really a hard place to be in because you don't have an identity that stands alone. Kubernetes itself had an identity that stood alone. It comes from this experience of running a system like this. It comes from research and white papers. It comes after previous attempts at solving this problem. So we agree that this problem needs to be solved. We know what layer it needs to be solved at. We just didn't get it right yet, so Kubernetes didn't necessarily try to get it right.It tried to start with only the primitives necessary to focus on the problem at hand. Now to your point, the extension interface of Kubernetes is what keeps it small. Years ago I remember plenty of meetings where we all got in rooms and said, "This thing is done." It doesn't need to be a PaaS. It doesn't need to compete with serverless platforms. The core of Kubernetes, like Linux, is largely done. Here's the core objects, and we're going to make a very great extension interface. We're going to make one for the container run time level so that way people can swap that out if they really want to, and we're going to do one that makes other APIs as first-class as ones we have, and we don't need to try to boil the ocean in every Kubernetes release. Everyone else has the ability to deploy extensions just like Linux, and I think that's why we're avoiding some of this tension in the vendor world because you don't have to change the core to get something that feels like a native part of Kubernetes.Corey: What do you think is currently being the most misinterpreted or misunderstood aspect of Kubernetes in the ecosystem?Kelsey: I think the biggest thing that's misunderstood is what Kubernetes actually is. And the thing that made it click for me, especially when I was writing the tutorial Kubernetes The Hard Way. I had to sit down and ask myself, "Where do you start trying to learn what Kubernetes is?" So I start with the database, right? The configuration store isn't Postgres, it isn't MySQL, it's Etcd. Why? Because we're not trying to be this generic data stores platform. We just need to store configuration data. Great. Now, do we let all the components talk to Etcd? No. We have this API server and between the API server and the chosen data store, that's essentially what Kubernetes is. You can stop there. At that point, you have a valid Kubernetes cluster and it can understand a few things. Like I can say, using the Kubernetes command-line tool, create this configuration map that stores configuration data and I can read it back.Great. Now I can't do a lot of things that are interesting with that. Maybe I just use it as a configuration store, but then if I want to build a container platform, I can install the Kubernetes kubelet agent on a bunch of machines and have it talk to the API server looking for other objects you add in the scheduler, all the other components. So what that means is that Kubernetes most important component is its API because that's how the whole system is built. It's actually a very simple system when you think about just those two components in isolation. If you want a container management tool that you need a scheduler, controller, manager, cloud provider integrations, and now you have a container tool. But let's say you want a service mesh platform. Well in a service mesh you have a data plane that can be Nginx or Envoy and that's going to handle routing traffic. And you need a control plane. That's going to be something that takes in configuration and it uses that to configure all the things in a data plane.Well, guess what? Kubernetes is 90% there in terms of a control plane, with just those two components, the API server, and the data store. So now when you want to build control planes, if you start with the Kubernetes API, we call it the API machinery, you're going to be 95% there. And then what do you get? You get a distributed system that can handle kind of failures on the back end, thanks to Etcd. You're going to get our backs or you can have permission on top of your schemas, and there's a built-in framework, we call it custom resource definitions that allows you to articulate a schema and then your own control loops provide meaning to that schema. And once you do those two things, you can build any platform you want. And I think that's one thing that it takes a while for people to understand that part of Kubernetes, that the thing we talk about today, for the most part, is just the first system that we built on top of this.Corey: I think that's a very far-reaching story with implications that I'm not entirely sure I am able to wrap my head around. I hope to see it, I really do. I mean you mentioned about writing Learn Kubernetes the Hard Way and your tutorial, which I'll link to in the show notes. I mean my, of course, sarcastic response to that recently was to register the domain Kubernetes the Easy Way and just re-pointed to Amazon's ECS, which is in no way shape or form Kubernetes and basically has the effect of irritating absolutely everyone as is my typical pattern of behavior on Twitter. But I have been meaning to dive into Kubernetes on a deeper level and the stuff that you've written, not just the online tutorial, both the books have always been my first port of call when it comes to that. The hard part, of course, is there's just never enough hours in the day.Kelsey: And one thing that I think about too is like the web. We have the internet, there's webpages, there's web browsers. Web Browsers talk to web servers over HTTP. There's verbs, there's bodies, there's headers. And if you look at it, that's like a very big complex system. If I were to extract out the protocol pieces, this concept of HTTP verbs, get, put, post and delete, this idea that I can put stuff in a body and I can give it headers to give it other meaning and semantics. If I just take those pieces, I can bill restful API's.Hell, I can even bill graph QL and those are just different systems built on the same API machinery that we call the internet or the web today. But you have to really dig into the details and pull that part out and you can build all kind of other platforms and I think that's what Kubernetes is. It's going to probably take people a little while longer to see that piece, but it's hidden in there and that's that piece that's going to be, like you said, it's going to probably be the foundation for building more control planes. And when people build control planes, I think if you think about it, maybe Fargate for EKS represents another control plane for making a serverless platform that takes to Kubernetes API, even though the implementation isn't what you find on GitHub.Corey: That's the truth. Whenever you see something as broadly adopted as Kubernetes, there's always the question of, "Okay, there's an awful lot of blog posts." Getting started to it, learn it in 10 minutes, I mean at some point, I'm sure there are some people still convince Kubernetes is, in fact, a breakfast cereal based upon what some of the stuff the CNCF has gotten up to. I wouldn't necessarily bet against it socks today, breakfast cereal tomorrow. But it's hard to find a decent level of quality, finding the certain quality bar of a trusted source to get started with is important. Some people believe in the hero's journey, story of a narrative building.I always prefer to go with the morons journey because I'm the moron. I touch technologies, I have no idea what they do and figure it out and go careening into edge and corner cases constantly. And by the end of it I have something that vaguely sort of works and my understanding's improved. But I've gone down so many terrible paths just by picking a bad point to get started. So everyone I've talked to who's actually good at things has pointed to your work in this space as being something that is authoritative and largely correct and given some of these people, that's high praise.Kelsey: Awesome. I'm going to put that on my next performance review as evidence of my success and impact.Corey: Absolutely. Grouchy people say, "It's all right," you know, for the right people that counts. If people want to learn more about what you're up to and see what you have to say, where can they find you?Kelsey: I aggregate most of outward interactions on Twitter, so I'm @KelseyHightower and my DMs are open, so I'm happy to field any questions and I attempt to answer as many as I can.Corey: Excellent. Thank you so much for taking the time to speak with me today. I appreciate it.Kelsey: Awesome. I was happy to be here.Corey: Kelsey Hightower, Principal Developer Advocate at Google. I'm Corey Quinn. This is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on Apple podcasts. If you've hated this podcast, please leave a five-star review on Apple podcasts and then leave a funny comment. Thanks.Announcer: This has been this week's episode of Screaming in the Cloud. You can also find more Core at screaminginthecloud.com or wherever fine snark is sold.Announcer: This has been a HumblePod production. Stay humble.

It's one thing to talk about your open source principles. It's another entirely to build them into your workflows. How does a large company like Amazon Web Services actually make it work? David Duncan, Sr Manager Partner Solutions Architect at AWS, explains that being open with partners and customers throughout the development process is key. He talks about ensuring there are no one-way doors, and how collaboration helps to produce a better experience for OpenShift on AWS as well as combining the power of the Cloud Control API with Ansible automation.

EuroBSDcon 2022 as first BSD conference, Red Hat's OpenShift vs FreeBSD Jails, Running a Docker Host under OpenBSD using vmd(8), history of sending signals to Unix process groups, Toolchains adventures - Q3 2022, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines EuroBSDCon 2022, my first BSD conference (and how they are different) (https://eerielinux.wordpress.com/2022/09/25/eurobsdcon-2022-my-first-bsd-conference-and-how-they-are-different/) Red Hat's OpenShift vs FreeBSD Jails (https://klarasystems.com/articles/red-hats-openshift-vs-freebsd-jails/) News Roundup The history of sending signals to Unix process groups (https://utcc.utoronto.ca/~cks/space/blog/unix/ProcessGroupsAndSignals) Running a Docker Host under OpenBSD using vmd(8) (https://www.tumfatig.net/2022/running-docker-host-openbsd-vmd/) Toolchains adventures - Q3 2022 (https://www.cambus.net/toolchains-adventures-q3-2022/) Beastie Bits -current has moved to 7.2 (https://undeadly.org/cgi?action=article;sid=20220912055003) Several /sbin daemons are now dynamically-linked (http://undeadly.org/cgi?action=article;sid=20220830052924) Announcing the pkgsrc 2022Q3 branch (https://mail-index.netbsd.org/netbsd-announce/2022/09/29/msg000341.html) Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Hans - datacenters and dust (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/476/feedback/Hans%20-%20datacenters%20and%20dust.md) Tim - Boot issue (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/476/feedback/Tim%20-%20Boot%20issue.md) aaron- dwm tiling (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/476/feedback/aaron-%20dwm%20tiling%20.md) *** Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

Our thoughts on IBM slicing up more of Red Hat, what stands out in Nextcloud Hub 3, and a few essential fixes finally landing in the Linux kernel.

Matt Butcher (@technosophos, Co-Founder/CEO @fermyontech) talks about building the next-generation PaaS platform around WebAssembly. SHOW: 633CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Datadog Kubernetes Solution: Maximum Visibility into Container EnvironmentsStart monitoring the health and performance of your container environment with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.Streamline on-call, collaboration, incident management, and automation with a free 30-day trial of Lightstep Incident Response, built on ServiceNow. Listeners of The Cloudcast will also receive a free Lightstep Incident Response T-shirt after firing an alert or incident.Pay for the services you use, not the number of people on your team with Lightstep Incident Response. Try free for 30 days. Fire an alert or incident today and receive a free Lightstep Incident Response t-shirt.SHOW NOTES:Fermyon (homepage)Fermyon launches WebAssembly PaaS platform (June 2022)Fermyon Open SourceFinicky Whiskers (WebAssembly game)Topic 1 - Welcome to the show. Let's talk about your background, as well as the team as Ferymon, as you all have some experience building application platforms.Topic 2 - Before we get into Fermyon, let's talk about WebAssembly. What is it, and how does it connect to your previous world of being heavily involved in containers and Kubernetes?Topic 3 - Let's talk about what it means to be a WebAssembly PaaS. We've seen PaaS platforms in the past (Deis, Heroku, dotCloud, Cloud Foundry, OpenShift, etc.). What do developers need to do, and what does the platform take care of? Topic 4 - Walk us through the Spin project and what it delivers? Can it be compared/contrasted to a container experience, or something else developers are familiar with?Topic 5 - What are some of the unique capabilities and use-cases where WebAssembly is a good fit and delivers unique value today?Topic 6 - How are people able to engage with Fermyon today?FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet