Podcasts about minikube

Riaan Nolan is a HashiCorp Ambassador that has developed Hashiqube, a DevOps development lab that runs all HashiCorp products. Hashiqube has a Docker daemon inside meaning we can run containers inside Hashiqube using Kubernetes (Minikube) or Nomad or Docker run. It runs all Hashicorp products: Vault, Terraform, Nomad, Consul, Waypoint, Boundary, Vagrant, Packer and Sentinel. It also runs a host of other popular Open Source DevOps/DevSecOps applications (Minikube, Ansible AWX Tower, Traefik etc.) showcasing how simple integration with Hashicorp products can result in tangible learnings and benefits for all its users. In this episode, we'll explore HashiQube on GitHub CodeSpaces. 00:00 Introductions 02:00 Introducing HashiQube

Bei Aktivitäten entstehen Ideen … bei den Nerds of Law war es eine Pizza, bei Glasskube Floorball, was, wie sich die Nerds erklären lassen, offenbar Sport ist. Gut, kann Pizza-essen sicher auch sein, aber darum geht es in der Folge nicht.    Vielmehr darum, was Glasskube jetzt eigentlich ist und warum Katharina sagt: “You had me at ‘Open Source' “.    Glasskube: https://glasskube.eu/   Github: https://github.com/glasskube/operator   Floorball (der Sport): https://de.wikipedia.org/wiki/Unihockey  Open Source (kein Sport, aber eine gute Idee): https://opensource.org  SaaS (auch kein Sport): https://www.oracle.com/de/applications/what-is-saas/  Jira: https://www.atlassian.com/de/software/jira  Confluence: https://www.atlassian.com/de/software/confluence  Kubernetes: https://kubernetes.io  Matomo: https://matomo.org  AVV: https://bisset.at/ (ja, da könnt ihr nachfragen)  Nerds-of-Law-Podcast-Folge 89: https://www.nerdsoflaw.com/2022/07/nerds-of-law-89-zum-jagen-tragen-mit-dorothea-wichert-nick/  Dogfooding (klingt schon wieder eher nach Sport): https://en.wikipedia.org/wiki/Eating_your_own_dog_food  Gitlab: https://about.gitlab.com  Minikube: https://kubernetes.io/de/docs/setup/minikube/  DuckDuckGo: https://duckduckgo.com  Penpot: https://penpot.app  Figma: https://www.figma.com/de  Miro: https://miro.com/de/  Garmin (Uhren): https://www.garmin.com/de-AT/c/wearables-smartwatches  Yaizo: https://www.yazio.com/de  Fairphone: https://www.fairphone.com/de/   Fußhängematte (Beispiel): https://www.gadget-rausch.de/fusshaengematten-so-entspannend-kann-bueroarbeit-sein/      Subscribe to the Podcast  RSS Feed https://nerdsoflaw.libsyn.com/rss   Apple Podcast https://podcasts.apple.com/de/podcast/nerds-of-law-podcast/id1506472002   SPOTIFY https://open.spotify.com/show/12D6osXfccI1bjAzapWzI4   Google Play Store https://playmusic.app.goo.gl/?ibi=com.google.PlayMusic&isi=691797987&ius=googleplaymusic&apn=com.google.android.music&link=https://play.google.com/music/m/Idvhwrimkmxb2phecnckyzik3qq?t%3DNerds_of_Law_Podcast%26pcampaignid%3DMKT-na-all-co-pr-mu-pod-16   YouTube https://www.youtube.com/playlist?list=PL7rmwzBy-IRGh8JkLCPIjyGMA-nHMtiAC   Deezer https://www.deezer.com/de/show/1138852     Nerds of Law®   http://www.nerdsoflaw.com   https://twitter.com/NerdsOfLaw   https://www.instagram.com/nerdsoflaw/   https://www.facebook.com/NerdsOfLaw/   Music by Mick Bordet www.mickbordet.com    Nerds of Law ® ist eine in Österreich registrierte Wortmarke.   

Join this episode of In the Nic of Time with Dan Lorenc, CEO, ChainGuard as they discuss the challenges and struggles around software supply chain and take a deep dive on Dan's incredible contributions to the open source community with his projects like Minikube, Sigstore, Distroless and Wolfi.

Show Notes:HelpSystems 2023 IBM i Marketplace Survey: https://rb.gy/z6xi0f Europese Commissie wil fabrikanten aansprakenlijk stellen bij schade door AI: https://tweakers.net/nieuws/201688/europese-commissie-wil-fabrikanten-aansprakelijk-stellen-bij-schade-door-ai.html Ferroelectric en piezoelectric materialen: https://phys.org/news/2022-09-unique-ferroelectric-microstructure-revealed.html Graph database: https://neo4j.com/developer/graph-database/ IBM Db2 HA: https://www.ibm.com/docs/en/db2/11.5?topic=server-db2-high-availability-feature IBM Db2 pureScale: https://www.ibm.com/docs/en/db2/10.5?topic=editions-introduction-db2-purescale-environment Db2 in containers: https://www.ibm.com/docs/en/db2/11.5?topic=db2-containerized-deployments Zelf aan de slag met OpenShift op je eigen pc, OpenShift local: https://developers.redhat.com/products/openshift-local/overview Db2 op OpenShift local: https://www.ibm.com/cloud/blog/deploy-the-db2-community-edition-operator-on-openshift-4x-using-red-hat-codeready-containers Db2 op Minikube, (Kubernetes op je pc): https://medium.com/@baheer/db2-on-kubernetes-8d715546f586Db2 op een AWS EKS cluster: https://www.ibm.com/support/pages/tutorial-adding-database-instance-aws-eks-cluster-using-db2-operator-0Gebruikte afkorting(en):XML: Extensible Markup LanguageJson: JavaScript Object NotationDBA: Database AdministratorSQL: Structured Query LanguageOp- en aanmerkingen kunnen gestuurd worden naar: ofjestoptdestekkererin@nl.ibm.com

Changelog The Code Quiz GitHub repository now has a basic mock API client that uses a JSON Server. This was installed on the Tuesdays Live stream Work has started on building a Vagrant box that houses MiniKube and the howtocodewell testing environments. Code Quiz GitHub Repository: https://github.com/howToCodeWell/code-quiz Building the Mock JSON API: https://youtu.be/OznPvJIjMDc JavaScript Code Quiz answers: https://youtu.be/Tyvmq3gyZMY Tips for newly appointed Web Development team leaders 1. How to manage your time when you are a coder and a manager? 2. Is it important for the lead to be the best coder in the team? 3. How to handle colleagues who are envious or felt that they should in the leader instead of you? 4. Do you need to know the whole system form top to bottom? My web development courses ➡️ Learn How to build a JavaScript Tip Calculator ➡️ Learn JavaScript arrays ➡️ Learn PHP arrays ➡️ Learn Python ✉️ Get my weekly newsletter ⏰ My current live coding schedule (Times are BST) Tuesdays 18:00 = Live Podcast YouTube Sundays 15:00 - Live coding on Twitch

Ask a developer about how they got into programming, and you learn so much about them. In this week's episode of The New Stack Makers, Chainguard founder Dan Lorenc said he got into programming halfway through college while studying mechanical engineering. "I got into programming because we had to do simulations and stuff in MATLAB," Lorenc said. And then I switched over to Python because it was similar. And we didn't need those licenses or whatever that we needed. And then I was like, Oh, this is much faster than you know, ordering parts and going to the machine shop and reserving time, so I got into it that way." It was three or four years ago that Lorenc got into the field of open source security. "Open source security and supply chain security weren't buzzwords back then," Lorenc said. "Nobody was talking about it. And I kind of got paranoid about it." Lorenc worked on the Minikube open source project at Google where he first saw how insecure it could be to work on open source projects. In the interview, he talks about the threats he saw in that work. It was so odd for Lorenc. State of art for open source security was not state of the art at all. It was the stone age. Lorenc said it felt weird for him to build the first release in MiniKube that did not raise questions about security. "But I mean, this is like a 200 megabyte Go binary that people were just running as root on their laptops across the Kubernetes community," Lorenc said. "And nobody had any idea what I put in there if it matched the source on GitHub or anything. So that was pretty terrifying. And that got me paranoid about the space and kind of went down this long rabbit hole that eventually resulted in starting Chainguard. Today, the world is burning down, and that's good for a security startup like Chainguard. "Yeah, we've got a mess of an industry to tackle here," Lorenc said. "If you've been following the news at all, it might seem like the software industry is burning on fire or falling down or anything because of all of these security problems. It's bad news for a lot of folks, but it's good news if you're in the security space." Good news, yes ,but how does it fit into a larger story? "Right now, one of our big focuses is figuring out how do we explain where we fit into the bigger landscape," Lorenc. said. "Because the security market is massive and confusing and full of vendors, putting buzzwords on their websites, like zero trust and stuff like that. And it's pretty easy to get lost in that mess. And so figuring out how we position ourselves, how we handle the branding, the marketing, and making it clear to prospective customers and community members, everything exactly what it is we do and what threats our products mitigate, to make sure we're being accurate there. And conveying that to our customers. That's my big focus right now."

This hour we focus on your feedback, Kubernetes, audio interfaces, and of course your weekly Linux headlines! -- During The Show -- 00:50 FreeCAD Thank You FreeCAD 03:00 Caller Matrix Bridge Hosting Bridges can break when cooperation is required on the other end 12:00 Kubernetes? - Tyler Grunt Work Kubernetes Crash Course (https://blog.gruntwork.io/a-crash-course-on-kubernetes-a96c3891ad82) Red Hat - Steve Ovens (https://www.redhat.com/sysadmin/users/steve-ovens) Kubernetes dropped Docker shim for CNI OpenShift (https://docs.openshift.com/) MiniKube (https://minikube.sigs.k8s.io/docs/) Mini Shift (https://github.com/MiniShift/minishift#documentation) OKD (UpStream OpenShift) (https://www.okd.io/) Steve's How Containers Work (https://www.redhat.com/sysadmin/building-container-namespaces) 24:26 News Wire OpenPGL Path Guiding Library Phoronix (https://www.phoronix.com/news/Intel-OpenPGL) MoonRay Renderer Open Source For U (https://www.opensourceforu.com/2022/08/dreamworks-animation-to-launch-moonray-renderer-as-open-source-software/) Hollywood Reporter (https://www.hollywoodreporter.com/business/digital/dreamworks-animation-release-renderer-open-source-software-1235192426/) VISTA 2.0 Open Source For U (https://www.opensourceforu.com/2022/08/the-latest-self-driving-car-algorithm-from-mit-is-open-source/) CMU auton-survival Mark Teck Post (https://www.marktechpost.com/2022/08/07/cmu-researchers-open-source-auton-survival-a-comprehensive-python-code-repository-of-user-friendly-machine-learning-tools-for-working-with-censored-time-to-event-data/) LLNL GridDS LLNL.GOV (https://www.llnl.gov/news/open-source-data-science-toolkit-energy-gridds) Godot 3.5 Gaming On Linux (https://www.gamingonlinux.com/2022/08/open-source-game-development-advances-with-godot-engine-35-out-now/) NanoScale Atomic Force Microscope Hackster.io (https://www.hackster.io/news/this-4-000-open-source-high-speed-atomic-force-microscope-is-a-nanoscale-imaging-marvel-69e5786fd824) CIFS/SMB3 just in time for Linux 6.0 Phoronix (https://www.phoronix.com/news/Linux-6.0-SM3-Client-Perf-MC) Elastic Search Alternative Manticore Search (https://manticoresearch.com/blog/manticore-alternative-to-elasticsearch/) New Ransomeware Targeting Linux Systems Info Security Magazine (https://www.infosecurity-magazine.com/news/gwisinlocker-ransomware-linux/) Bleeping Computer (https://www.bleepingcomputer.com/news/security/new-gwisinlocker-ransomware-encrypts-windows-and-linux-esxi-servers/) New IoT Malware RapperBot The Hacker News (https://thehackernews.com/2022/08/new-iot-rapperbot-malware-targeting.html) Tails 5.3.1 Emergency Release TorProject (https://forum.torproject.net/t/tails-5-3-1-is-out-2022-08-02/4184) 26:28 Audio Interfaces? - Thor Lexicon Alpha Change the Default Sample Rate on Pipewire (ArchWiki) (https://wiki.archlinux.org/title/PipeWire#Changing_the_default_sample_rate) 30:16 Bluray Playback on old computer? - William Amazon Link (https://www.amazon.com/Blu-ray-ThinkPad-Workstation-Optical-Replacement/dp/B081XLNX3H/?tag=minddripmedia-20) Ebay Link 1 (https://www.ebay.com/itm/151236944357) Ebay Link 2 (https://www.ebay.com/itm/293675206709) BUS Speed may limit the drive bay Don't buy T series parts for a E series Why use optical media? MakeMKV (https://makemkv.com/) Big Buck Bunny (https://peach.blender.org/) 38:00 Linux Delta Website? - Lou How did you create the Linux Delta website Noah didn't build Linux Delta Brad Wilson KhronoSync (https://khronosync.com/) Linux Delta website code (https://gitlab.com/altispeed/mdm/dev/linux-delta) 39:50 Thornbill Asks Is Invoice Ninja still the recommended solution for invoicing? Noah's Frustrations 43:20 Pick of the Week DICOM Viewer Weasis (https://nroduit.github.io/en/) History of DICOM What is DICOM DCM4CHEE (PACS) GitHub (https://github.com/dcm4che/dcm4chee-arc-light) Atlassian EE2 Overview (https://dcm4che.atlassian.net/wiki/spaces/ee2/overview) J4Care.com (https://www.j4care.com/dcm4che.html) -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/298) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed) Special Guest: Steve Ovens.

Cet épisode marathon sera découpé en deux morceaux pour éviter à vos oreilles une écoute marathon. Dans cet épisode on y parle Brian Goetz, Bian Goetz, Brian Goetz, usages des threads virtuels, OpenAPI, Kubernetes, KNative, copilot et Tekton. La deuxième partie couvrira des sujets d'architecture et de loi société et organisation ainsi que les conférences à venir. Enregistré le 8 juillet 2022 Téléchargement de l'épisode LesCastCodeurs-Episode–281.mp3 News Langages Peut-être une nouvelle syntaxe spécifique aux Records Java pour tordre le cou aux builders Brian Goetz discute de l'idée d'avoir une syntaxe spécifique pour les records pour facilement créer un record dérivé, potentiellement avec des valeurs par défaut, mais en paramétrant certains champs Point shadowPos = shape.position() with { x = 0 } Cela évite de créer la notion de paramètre par défaut dans les constructeurs ou les méthodes Il y a l'article Data Oriented Programming de Brian Goetz, sur InfoQ projet Amber amène des changements qui combinés permet de faire du data oriented programming en Java et pas que du OOP OO combine état et comportement (code) OO est super utile pour défendre des limites (programme large en des limites plus petites et plus gérable) mais on s'oriente vers des applications plus petites (microservices) data oriented programming: modélise data immuable et le code de la logique métier est séparée records -> data en tant que classe, sealed classes -> définir des choix, pattern matching -> raisonne sur des data polymorphiques algebraic data: hiérarchie de sealed classes dont les feuilles sont des records: nommées, immuable, testable (pas de code) Un nouveau JEP pour intégrer une Classfile API Le JDK inclut déjà des forks de ASM, de BCEL, et d'autres APIs internes, pour manipuler / produire / lire le bytecode Mais l'idée ici c'est que le JDK vienne avec sa propre API officielle, et qui soit plus sympa à utiliser aussi que le pattern visiteur de ASM par exemple La version d'ASM intégrée était toujours en retard d'une version (problème de poule et d'oeuf, car ASM doit supporter la dernière version de Java, mais Java n+1 n'est pas encore sorti) Lilian nous montre à quoi va ressembler les Record Patterns de JEP 405 Apache Groovy et les virtual threads, et aussi Groovy et le Deep Learning Paul King, qui dirige actuellement le PMC de Apache Groovy, a partagé récemment plusieurs articles sur le blog d'Apache sur des intégrations intéressantes avec Groovy Groovy et sa librairie GPars pour la programmation concurrente et parallèle s'intègre facilement avec les Virtual Threads de JEP 425 / JDK 19 https://blogs.apache.org/groovy/entry/gpars-meets-virtual-threads Groovy avec Apache Wayang et Apache Spark pour classifier des Whiskey par clusterisation KMeans https://blogs.apache.org/groovy/entry/using-groovy-with-apache-wayang Et aussi Groovy avec différentes librairies de Deep Learning pour la classification https://blogs.apache.org/groovy/entry/classifying-iris-flowers-with-deep Le jargon (en anglais) de la programmation fonctionnelle, si vous avez rêvé d'avoir sous la main la définition de foncteur, de monoïde, et j'en passe avec des exemples en JavaScript des pointeurs vers des librairies fonctionnelles en JavaScript des traductions dans d'autres langues et d'autres langages de programmation Librairies Spring Boot 2.7 SpringBoot 2.7 Spring GraphQL 1.0 Support pour Podman Gestion de dépendance et auto configuration pour Cache2k nouvelle annotations pour Elasticsearch et CouchBase dernière versions avant SpringBoot 3 qui changera plus de choses. Recommande de migrer une version a la fois. Support pour 2.5 à fini (upstream) Quarkus 2.10.0 Travaux préliminaires sur les threads virtuels de Loom Support non-blocking pour GraphQL Prise en charge des Kubernetes service binding pour les clients SQL réactifs CacheKeyGenerator pour l'extension de cache quarkus-bootstrap-maven-plugin déprécié et remplacé par quarkus-extension-maven-plugin (uniquement utile pour les développeurs d'extensions Quarkus) Nouveaux guides: Using Stork with Kubernetes OpenId Connect Client Reference Guide Using Podman with Quarkus Les différences entre OpenAPI 2 et 3 Introduction de la notion de lien pour créer des relations entre Response et Operations, pratique pour faire des APIs hypermédia La structure du document OpenAPI a été -un peu simplifiée, en combinant par exemple basePath et schemes, ou en rassemblant les securityDefinitions Des améliorations sur les security schemes, autour de OAuth et OpenID Plus de clarté dans la négociation de contenu et les cookies La section des exemples de Request / Response devrait aider les outils qui génèrent par exemple des SDK automatiquement à partir de la description OpenAPI Un support étendu de JSON Schema Introduction d'une notion de Callback, importante pour les APIs asynchrones, en particulier les WebHooks je me demande si ils ont l'intention d'embrasser AsyncAPI ou su la partie asynchrone d'OpenAPI 3 a pour objectif de faire de la competition Infrastructure N'utilisez pas Kubernetes tout de suite ! Kubernetes, c'est bien, mais c'est un gros marteau. Est-ce que vous avez des gros clous à enfoncer ? Ne commencez peut-être pas avec l'artillerie lourde de Kubernetes. Commencez plutôt avec des solutions managées genre serverless, ce sera plus simple, et au fur et à mesure si votre infrastructure a besoin de grossir et dépasse les fonctionnalités des solutions managées, à ce moment là seulement évaluer si Kubernetes peut répondre à votre besoin Choisir Kubernetes, c'est aussi avoir la taille de l'équipe qui va bien avec, et il faut des profils DevOps, SRE, etc, pour gérer un cluster K8S L'auteur suggère grosso modo que ça dépend de l'ordre de magnitude de la taille de l'équipe : avec quelques personnes, préférez des solutions type Google App Engine ou AWS App Runner, avec une dizaine de personne peut-être du Google Cloud Run ou AWS Fargate, avec moins d'une centaine là pourquoi pas du Kubernetes managé comme Google Kubernetes Engine, et si vous dépassez mille, alors peut-être vos propres clusters managés par vos soins et hébergés par vos soins sur votre infra ca impose d'utiliser les services du cloud provider? Parce que la vie ce n'est pas que du code maison. C'est la mode de dire de pas utiliser K8S : https://www.jeremybrown.tech/8-kubernetes-is-a-red-flag-signalling-premature-optimisation/ (mais bon, vu le nombre de fois où il est pas utilisé à b Knative Eventing Devlivery methods on peut faire de la delviery simple 1–1 sans garantie on peut faire de la delivery complexe et persistante en introduisant la notion de channel qui decouple la source de la destination. on peut repondre a la reception d'un message et pousser la réponse dans un second channel mais ca devient compliquer a gérer quand on rajoute des souscripteurs il y a la notiuon de broker qui definit: des flitres, un channel (automatique) et la capacité de répondre les triggers sont un abonnement non pas a un channel mais a un type d'évènement spécifique Cloud AWS is Windows and Kube is Linux pourquoi utilisez Kube qui etait pas stablewa lors qu'AWS offre tout AWS forcé d'offrir EKS MAis pourri Lockin AWSIAM Pourquoi AWS serait le windows economies d'echelles de faire chez soi kube devient rentable une certaine taille de l'organisation besoin alternative a AWS (bus factor) on voit le Kube distro modele arriver Google data center Paris Outillage IntelliJ IDEA 2022.5 EAP 5 amène des nouveautés Frameworks and Technologies Spring 6 and Spring Boot 3 Support for new declarative HTTP Clients in Spring 6 URL completion and navigation for Spring Cloud Gateway routes Experimental GraalVM Native Debugger for Java Code insight improvements for JVM microservices test and mock frameworks Code insight improvements for Spring Shell Improved support for JAX-RS endpoints Support for WebSockets endpoints in HTTP Client Support for GraphQL endpoints in the HTTP Client UI/UX improvements for the HTTP Client Improved navigation between Protobuf and Java sources Kubernetes and Docker Intercept Kubernetes service requests with Telepresence integration Upload local Docker image to Minikube and other connections Docker auto-connection at IDE restart Docker connection options for different docker daemons GitHub copilot est disponible pour tous (les developpeurs) 40% du code écrit est généré par copilot en python (ca calme) gratuit pour les étudiants et les développeurs OSS Revue de Redmonk décrit copilot comme une extension d'intelligence ou auto complete mais qui « comprend » le code autour premiere fois pas une boite de cette taille et à cette échelle l'avantage de copilot en terme de productivité, de qualité de code, de sécurité et de légalité En gros, c'est encore à voir. Mais la qualité impressionne les gens qui l'ont testé ; sécurité pas de retour d'un côté ou de l'autre sauf que les développeurs humains ne sont pas des lumières de sécurité :D GitHub pense que GitHub n'est pas responsable de la violation de code vue que ce sont des machines et des algorithmes qui transforment: cela a l'air d'etre le consensus des avocats GitHub dit qu'on est responsable du code qu'on écrit avec copilot Et implicitement GitHub dit que la licensure du code « source » ne se propage pas au code generé. Et là, c'est pas clair et de la responsibilité de l'utilisateur, mais la encore les avocats sont plutot ok moralement c'est probablement pas ok mais bon et il y a débat autour des licenses copyleft notamment LGPL 1% du temps, code copié verbatim de > 150 caractères Question sur le code non open source sur lequel GitHub Copilot s'appuie mais en gros le marcher s'en fout un peu des licences Risque de reputation de Microsoft la question c'est quand / si les gens seront prêt à accepter cet usage Gradle publie sa roadmap Historiquement, la société Gradle Inc ne publiait pas vraiment de roadmap officielle Outre les tickets que l'on pouvait voir dans Github, cette fois ci, une “roadmap board” est visible et disponible pour tout le monde, et pas seulement pour les clients Tekton est groovy (mais non, il n'utilise pas Groovy !) Un grand tutoriel sur Tekton Une brève histoire de CI/CD (avec un contraste avec Groovy utilisé dans Jenkins) Un aperçu des grands concepts de Tekton, avec ses tâches et ses pipelines (Task, TaskRun, Pipeline, PipelineRun) Comment installer Tekton Les outils CLI Un exemple concret d'utilisation Sortie de Vim 9, surtout avec VimScript 9 des changements incompatibles entre VimScript 8.2 et 9 font qu'il était nécessaire de passer à une version majeure mais l'ancienne version du langage reste supportée pour compatibilité avec la nouvelle, les utilisateurs peuvent s'attendre à des performances x10 voire x100 ! le langage devient pré-compilé, au lieu d'être interprété ligne par ligne l'idée était d'avoir un langage plus proche de ce qu'on trouve dans JavaScript, TypeScript ou Java Conférences De la part de Youen Cette année Codeurs en Seine, c'est le 17 novembre et le cfp est ouvert N'hésitez pas à amener un peu de JVM dans l'appel à orateur. (ca commence à se faire rare). Pour rappel : codeurs en seine c'est 1000 personnes autour des métiers du développement dans une des plus grande salle de Rouen, le kindarena. Nous contacter Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Faire un crowdcast ou une crowdquestion Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/

Docker und Container sind immer schon Hand in Hand gegangen. Wir sprechen ein wenig über die Geschichte aber vor allem auch die Änderungen im Docker Hub (https://www.docker.com/increase-rate-limits) und Docker Desktop (https://www.docker.com/blog/updating-product-subscriptions/). Wo vor November 2020 viele noch Unternehmen nicht daran gedacht haben eine eigene Registry oder zumindest einen Pull Through Cache (https://docs.docker.com/registry/recipes/mirror/) aufzubauen sind diese heute oft fester Bestandteil von Containerumgebungen. Besonders Docker Desktop und die Alternativen dazu haben uns in den letzten Monaten beschäftigt, weshalb wir gern die gewonnenen Informationen teilen möchten. Die Gäste dieser Episode sind Jasper Wiegratz und René Keller. Gemeinsam reden wir über die Alternativen die wir gefunden haben und besprechen unsere Individuellen Use-Cases. Außerdem besprechen wir, ob ein Wechsel überhaupt notwendig ist. Hier gehts zu weiteren Informationen: https://kubernetespodcast.com/episode/168-rancher-desktop/https://rancherdesktop.io/https://www.docker.com/products/docker-desktophttps://minikube.sigs.k8s.io/docs/https://github.com/lima-vm/limahttps://podman.io/getting-started/installationJaspers Lima Stack https://gist.github.com/jwhb/febeb3d90790c08d5dddc6eba0c2f06d

Docker und Container sind immer schon Hand in Hand gegangen. Wir sprechen ein wenig über die Geschichte aber vor allem auch die Änderungen im Docker Hub (https://www.docker.com/increase-rate-limits) und Docker Desktop (https://www.docker.com/blog/updating-product-subscriptions/). Wo vor November 2020 viele noch Unternehmen nicht daran gedacht haben eine eigene Registry oder zumindest einen Pull Through Cache (https://docs.docker.com/registry/recipes/mirror/) aufzubauen sind diese heute oft fester Bestandteil von Containerumgebungen. Besonders Docker Desktop und die Alternativen dazu haben uns in den letzten Monaten beschäftigt, weshalb wir gern die gewonnenen Informationen teilen möchten. Die Gäste dieser Episode sind Jasper Wiegratz und René Keller. Gemeinsam reden wir über die Alternativen die wir gefunden haben und besprechen unsere Individuellen Use-Cases. Außerdem besprechen wir, ob ein Wechsel überhaupt notwendig ist. Hier gehts zu weiteren Informationen: https://kubernetespodcast.com/episode/168-rancher-desktop/https://rancherdesktop.io/https://www.docker.com/products/docker-desktophttps://minikube.sigs.k8s.io/docs/https://github.com/lima-vm/limahttps://podman.io/getting-started/installationJaspers Lima Stack https://gist.github.com/jwhb/febeb3d90790c08d5dddc6eba0c2f06d

In dieser Folge sprechen wir über VMware Tanzu, der Kubernetes Lösung von VMware. Die Folge ist die zweite Folge unserer Serie zu VMware Tanzu. Wir betrachten wofür man Tanzu und K8s einsetzen kann. Außerdem sprechen wir über Business Cases und Automatisierung, wie man ins Thema startet, wie man Hands On bekommt, über Weiterbildungsmaterial und Proof of Concept. Wir wünschen euch viel Spaß beim hören! Hier noch die versprochenen Links: Buchtipp von Nico und JP https://www.amazon.de/Kubernetes-Action-Marko-Luksa/dp/1617293725 VMware Hands on Labs (HOL) https://hol.vmware.com/ Tanzu Community Edition https://tanzucommunityedition.io/ Minikube https://minikube.sigs.k8s.io/docs/ K3s https://k3s.io/ Alex Ellis Library https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/ Cloud Native Computing Foundation (CNCF) Projekte https://www.cncf.io/projects/ Cover, Logo, Schrift und unsere Gesichter als Cartoon sind von der Lieben Amina (https://aminaabukarim.artstation.com/)

About ABAB Periasamy is the co-founder and CEO of MinIO, an open source provider of high performance, object storage software. In addition to this role, AB is an active investor and advisor to a wide range of technology companies, from H2O.ai and Manetu where he serves on the board to advisor or investor roles with Humio, Isovalent, Starburst, Yugabyte, Tetrate, Postman, Storj, Procurify, and Helpshift. Successful exits include Gitter.im (Gitlab), Treasure Data (ARM) and Fastor (SMART).AB co-founded Gluster in 2005 to commoditize scalable storage systems. As CTO, he was the primary architect and strategist for the development of the Gluster file system, a pioneer in software defined storage. After the company was acquired by Red Hat in 2011, AB joined Red Hat's Office of the CTO. Prior to Gluster, AB was CTO of California Digital Corporation, where his work led to scaling of the commodity cluster computing to supercomputing class performance. His work there resulted in the development of Lawrence Livermore Laboratory's “Thunder” code, which, at the time was the second fastest in the world.  AB holds a Computer Science Engineering degree from Annamalai University, Tamil Nadu, India.AB is one of the leading proponents and thinkers on the subject of open source software - articulating the difference between the philosophy and business model. An active contributor to a number of open source projects, he is a board member of India's Free Software Foundation.Links: MinIO: https://min.io/ Twitter: https://twitter.com/abperiasamy MinIO Slack channel: https://minio.slack.com/join/shared_invite/zt-11qsphhj7-HpmNOaIh14LHGrmndrhocA LinkedIn: https://www.linkedin.com/in/abperiasamy/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, 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 sponsored in part by our friends at Sysdig. Sysdig is the solution for securing DevOps. They have a blog post that went up recently about how an insecure AWS Lambda function could be used as a pivot point to get access into your environment. They've also gone deep in-depth with a bunch of other approaches to how DevOps and security are inextricably linked. To learn more, visit sysdig.com and tell them I sent you. That's S-Y-S-D-I-G dot com. My thanks to them for their continued support of this ridiculous nonsense.Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is, in AWS, with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem, and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai, and Stax have seen significant results by using them, and it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.in a siloCorey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by someone who's doing something a bit off the beaten path when we talk about cloud. I've often said that S3 is sort of a modern wonder of the world. It was the first AWS service brought into general availability. Today's promoted guest is the co-founder and CEO of MinIO, Anand Babu Periasamy, or AB as he often goes, depending upon who's talking to him. Thank you so much for taking the time to speak with me today.AB: It's wonderful to be here, Corey. Thank you for having me.Corey: So, I want to start with the obvious thing, where you take a look at what is the cloud and you can talk about AWS's ridiculous high-level managed services, like Amazon Chime. Great, we all see how that plays out. And those are the higher-level offerings, ideally aimed at problems customers have, but then they also have the baseline building blocks services, and it's hard to think of a more baseline building block than an object store. That's something every cloud provider has, regardless of how many scare quotes there are around the word cloud; everyone offers the object store. And your solution is to look at this and say, “Ah, that's a market ripe for disruption. We're going to build through an open-source community software that emulates an object store.” I would be sitting here, more or less poking fun at the idea except for the fact that you're a billion-dollar company now.AB: Yeah.Corey: How did you get here?AB: So, when we started, right, we did not actually think about cloud that way, right? “Cloud, it's a hot trend, and let's go disrupt is like that. It will lead to a lot of opportunity.” Certainly, it's true, it lead to the M&S, right, but that's not how we looked at it, right? It's a bad idea to build startups for M&A.When we looked at the problem, when we got back into this—my previous background, some may not know that it's actually a distributed file system background in the open-source space.Corey: Yeah, you were one of the co-founders of Gluster—AB: Yeah.Corey: —which I have only begrudgingly forgiven you. But please continue.AB: [laugh]. And back then we got the idea right, but the timing was wrong. And I had—while the data was beginning to grow at a crazy rate, end of the day, GlusterFS has to still look like an FS, it has to look like a file system like NetApp or EMC, and it was hugely limiting what we can do with it. The biggest problem for me was legacy systems. I have to build a modern system that is compatible with a legacy architecture, you cannot innovate.And that is where when Amazon introduced S3, back then, like, when S3 came, cloud was not big at all, right? When I look at it, the most important message of the cloud was Amazon basically threw everything that is legacy. It's not [iSCSI 00:03:21] as a Service; it's not even FTP as a Service, right? They came up with a simple, RESTful API to store your blobs, whether it's JavaScript, Android, iOS, or [AAML 00:03:30] application, or even Snowflake-type application.Corey: Oh, we spent ten years rewriting our apps to speak object store, and then they released EFS, which is NFS in the cloud. It's—AB: Yeah.Corey: —I didn't realize I could have just been stubborn and waited, and the whole problem would solve itself. But here we are. You're quite right.AB: Yeah. And even EFS and EBS are more for legacy stock can come in, buy some time, but that's not how you should stay on AWS, right? When Amazon did that, for me, that was the opportunity. I saw that… while world is going to continue to produce lots and lots of data, if I built a brand around that, I'm not going to go wrong.The problem is data at scale. And what do I do there? The opportunity I saw was, Amazon solved one of the largest problems for a long time. All the legacy systems, legacy protocols, they convinced the industry, throw them away and then start all over from scratch with the new API. While it's not compatible, it's not standard, it is ridiculously simple compared to anything else.No fstabs, no [unintelligible 00:04:27], no [root 00:04:28], nothing, right? From any application anywhere you can access was a big deal. When I saw that, I was like, “Thank you Amazon.” And I also knew Amazon would convince the industry that rewriting their application is going to be better and faster and cheaper than retrofitting legacy applications.Corey: I wonder how much that's retconned because talking to some of the people involved in the early days, they were not at all convinced they [laugh] would be able to convince the industry to do this.AB: Actually, if you talk to the analyst reporters, the IDC's, Gartner's of the world to the enterprise IT, the VMware community, they would say, “Hell no.” But if you talk to the actual application developers, data infrastructure, data architects, the actual consumers of data, for them, it was so obvious. They actually did not know how to write an fstab. The iSCSI and NFS, you can't even access across the internet, and the modern applications, they ran across the globe, in JavaScript, and all kinds of apps on the device. From [Snap 00:05:21] to Snowflake, today is built on object store. It was more natural for the applications team, but not from the infrastructure team. So, who you asked that mattered.But nevertheless, Amazon convinced the rest of the world, and our bet was that if this is going to be the future, then this is also our opportunity. S3 is going to be limited because it only runs inside AWS. Bulk of the world's data is produced everywhere and only a tiny fraction will go to AWS. And where will the rest of the data go? Not SAN, NAS, HDFS, or other blob store, Azure Blob, or GCS; it's not going to be fragmented. And if we built a better object store, lightweight, faster, simpler, but fully compatible with S3 API, we can sweep and consolidate the market. And that's what happened.Corey: And there is a lot of validity to that. We take a look across the industry, when we look at various standards—I mean, one of the big problems with multi-cloud in many respects is the APIs are not quite similar enough. And worse, the failure patterns are very different, of I don't just need to know how the load balancer works, I need to know how it breaks so I can detect and plan for that. And then you've got the whole identity problem as well, where you're trying to manage across different frames of reference as you go between providers, and leads to a bit of a mess. What is it that makes MinIO something that has been not just something that has endured since it was created, but clearly been thriving?AB: The real reason, actually is not the multi-cloud compatibility, all that, right? Like, while today, it is a big deal for the users because the deployments have grown into 10-plus petabytes, and now the infrastructure team is taking it over and consolidating across the enterprise, so now they are talking about which key management server for storing the encrypted keys, which key management server should I talk to? Look at AWS, Google, or Azure, everyone has their own proprietary API. Outside they, have [YAML2 00:07:18], HashiCorp Vault, and, like, there is no standard here. It is supposed to be a [KMIP 00:07:23] standard, but in reality, it is not. Even different versions of Vault, there are incompatibilities for us.That is where—like from Key Management Server, Identity Management Server, right, like, everything that you speak around, how do you talk to different ecosystem? That, actually, MinIO provides connectors; having the large ecosystem support and large community, we are able to address all that. Once you bring MinIO into your application stack like you would bring Elasticsearch or MongoDB or anything else as a container, your application stack is just a Kubernetes YAML file, and you roll it out on any cloud, it becomes easier for them, they're able to go to any cloud they want. But the real reason why it succeeded was not that. They actually wrote their applications as containers on Minikube, then they will push it on a CI/CD environment.They never wrote code on EC2 or ECS writing objects on S3, and they don't like the idea of [past 00:08:15], where someone is telling you just—like you saw Google App Engine never took off, right? They liked the idea, here are my building blocks. And then I would stitch them together and build my application. We were part of their application development since early days, and when the application matured, it was hard to remove. It is very much like Microsoft Windows when it grew, even though the desktop was Microsoft Windows Server was NetWare, NetWare lost the game, right?We got the ecosystem, and it was actually developer productivity, convenience, that really helped. The simplicity of MinIO, today, they are arguing that deploying MinIO inside AWS is easier through their YAML and containers than going to AWS Console and figuring out how to do it.Corey: As you take a look at how customers are adopting this, it's clear that there is some shift in this because I could see the story for something like MinIO making an awful lot of sense in a data center environment because otherwise, it's, “Great. I need to make this app work with my SAN as well as an object store.” And that's sort of a non-starter for obvious reasons. But now you're available through cloud marketplaces directly.AB: Yeah.Corey: How are you seeing adoption patterns and interactions from customers changing as the industry continues to evolve?AB: Yeah, actually, that is how my thinking was when I started. If you are inside AWS, I would myself tell them that why don't use AWS S3? And it made a lot of sense if it's on a colo or your own infrastructure, then there is an object store. It even made a lot of sense if you are deploying on Google Cloud, Azure, Alibaba Cloud, Oracle Cloud, it made a lot of sense because you wanted an S3 compatible object store. Inside AWS, why would you do it, if there is AWS S3?Nowadays, I hear funny arguments, too. They like, “Oh, I didn't know that I could use S3. Is S3 MinIO compatible?” Because they will be like, “It came along with the GitLab or GitHub Enterprise, a part of the application stack.” They didn't even know that they could actually switch it over.And otherwise, most of the time, they developed it on MinIO, now they are too lazy to switch over. That also happens. But the real reason that why it became serious for me—I ignored that the public cloud commercialization; I encouraged the community adoption. And it grew to more than a million instances, like across the cloud, like small and large, but when they start talking about paying us serious dollars, then I took it seriously. And then when I start asking them, why would you guys do it, then I got to know the real reason why they wanted to do was they want to be detached from the cloud infrastructure provider.They want to look at cloud as CPU network and drive as a service. And running their own enterprise IT was more expensive than adopting public cloud, it was productivity for them, reducing the infrastructure, people cost was a lot. It made economic sense.Corey: Oh, people always cost more the infrastructure itself does.AB: Exactly right. 70, 80%, like, goes into people, right? And enterprise IT is too slow. They cannot innovate fast, and all of those problems. But what I found was for us, while we actually build the community and customers, if you're on AWS, if you're running MinIO on EBS, EBS is three times more expensive than S3.Corey: Or a single copy of it, too, where if you're trying to go multi-AZ and you have the replication traffic, and not to mention you have to over-provision it, which is a bit of a different story as well. So, like, it winds up being something on the order of 30 times more expensive, in many cases, to do it right. So, I'm looking at this going, the economics of running this purely by itself in AWS don't make sense to me—long experience teaches me the next question of, “What am I missing?” Not, “That's ridiculous and you're doing it wrong.” There's clearly something I'm not getting. What am I missing?AB: I was telling them until we made some changes, right—because we saw a couple of things happen. I was initially like, [unintelligible 00:12:00] does not make 30 copies. It makes, like, 1.4x, 1.6x.But still, the underlying block storage is not only three times more expensive than S3, it's also slow. It's a network storage. Trying to put an object store on top of it, another, like, software-defined SAN, like EBS made no sense to me. Smaller deployments, it's okay, but you should never scale that on EBS. So, it did not make economic sense. I would never take it seriously because it would never help them grow to scale.But what changed in recent times? Amazon saw that this was not only a problem for MinIO-type players. Every database out there today, every modern database, even the message queues like Kafka, they all have gone scale-out. And they all depend on local block store and putting a scale-out distributed database, data processing engines on top of EBS would not scale. And Amazon introduced storage optimized instances. Essentially, that reduced to bet—the data infrastructure guy, data engineer, or application developer asking IT, “I want a SuperMicro, or Dell server, or even virtual machines.” That's too slow, too inefficient.They can provision these storage machines on demand, and then I can do it through Kubernetes. These two changes, all the public cloud players now adopted Kubernetes as the standard, and they have to stick to the Kubernetes API standard. If they are incompatible, they won't get adopted. And storage optimized that is local drives, these are machines, like, [I3 EN 00:13:23], like, 24 drives, they have SSDs, and fast network—like, 25-gigabit 200-gigabit type network—availability of these machines, like, what typically would run any database, HDFS cluster, MinIO, all of them, those machines are now available just like any other EC2 instance.They are efficient. You can actually put MinIO side by side to S3 and still be price competitive. And Amazon wants to—like, just like their retail marketplace, they want to compete and be open. They have enabled it. In that sense, Amazon is actually helping us. And it turned out that now I can help customers build multiple petabyte infrastructure on Amazon and still stay efficient, still stay price competitive.Corey: I would have said for a long time that if you were to ask me to build out the lingua franca of all the different cloud providers into a common API, the S3 API would be one of them. Now, you are building this out, multi-cloud, you're in all three of the major cloud marketplaces, and the way that you do that and do those deployments seems like it is the modern multi-cloud API of Kubernetes. When you first started building this, Kubernetes was very early on. What was the evolution of getting there? Or were you one of the first early-adoption customers in a Kubernetes space?AB: So, when we started, there was no Kubernetes. But we saw the problem was very clear. And there was containers, and then came Docker Compose and Swarm. Then there was Mesos, Cloud Foundry, you name it, right? Like, there was many solutions all the way up to even VMware trying to get into that space.And what did we do? Early on, I couldn't choose. I couldn't—it's not in our hands, right, who is going to be the winner, so we just simply embrace everybody. It was also tiring that to allow implement native connectors to all of them different orchestration, like Pivotal Cloud Foundry alone, they have their own standard open service broker that's only popular inside their system. Go outside elsewhere, everybody was incompatible.And outside that, even, Chef Ansible Puppet scripts, too. We just simply embraced everybody until the dust settle down. When it settled down, clearly a declarative model of Kubernetes became easier. Also Kubernetes developers understood the community well. And coming from Borg, I think they understood the right architecture. And also written in Go, unlike Java, right?It actually matters, these minute new details resonating with the infrastructure community. It took off, and then that helped us immensely. Now, it's not only Kubernetes is popular, it has become the standard, from VMware to OpenShift to all the public cloud providers, GKS, AKS, EKS, whatever, right—GKE. All of them now are basically Kubernetes standard. It made not only our life easier, it made every other [ISV 00:16:11], other open-source project, everybody now can finally write one code that can be operated portably.It is a big shift. It is not because we chose; we just watched all this, we were riding along the way. And then because we resonated with the infrastructure community, modern infrastructure is dominated by open-source. We were also the leading open-source object store, and as Kubernetes community adopted us, we were naturally embraced by the community.Corey: Back when AWS first launched with S3 as its first offering, there were a bunch of folks who were super excited, but object stores didn't make a lot of sense to them intrinsically, so they looked into this and, “Ah, I can build a file system and users base on top of S3.” And the reaction was, “Holy God don't do that.” And the way that AWS decided to discourage that behavior is a per request charge, which for most workloads is fine, whatever, but there are some that causes a significant burden. With running something like MinIO in a self-hosted way, suddenly that costing doesn't exist in the same way. Does that open the door again to so now I can use it as a file system again, in which case that just seems like using the local file system, only with extra steps?AB: Yeah.Corey: Do you see patterns that are emerging with customers' use of MinIO that you would not see with the quote-unquote, “Provider's” quote-unquote, “Native” object storage option, or do the patterns mostly look the same?AB: Yeah, if you took an application that ran on file and block and brought it over to object storage, that makes sense. But something that is competing with object store or a layer below object store, that is—end of the day that drives our block devices, you have a block interface, right—trying to bring SAN or NAS on top of object store is actually a step backwards. They completely missed the message that Amazon told that if you brought a file system interface on top of object store, you missed the point, that you are now bringing the legacy things that Amazon intentionally removed from the infrastructure. Trying to bring them on top doesn't make it any better. If you are arguing from a compatibility some legacy applications, sure, but writing a file system on top of object store will never be better than NetApp, EMC, like EMC Isilon, or anything else. Or even GlusterFS, right?But if you want a file system, I always tell the community, they ask us, “Why don't you add an FS option and do a multi-protocol system?” I tell them that the whole point of S3 is to remove all those legacy APIs. If I added POSIX, then I'll be a mediocre object storage and a terrible file system. I would never do that. But why not write a FUSE file system, right? Like, S3Fs is there.In fact, initially, for legacy compatibility, we wrote MinFS and I had to hide it. We actually archived the repository because immediately people started using it. Even simple things like end of the day, can I use Unix [Coreutils 00:19:03] like [cp, ls 00:19:04], like, all these tools I'm familiar with? If it's not file system object storage that S3 [CMD 00:19:08] or AWS CLI is, like, to bloatware. And it's not really Unix-like feeling.Then what I told them, “I'll give you a BusyBox like a single static binary, and it will give you all the Unix tools that works for local filesystem as well as object store.” That's where the [MC tool 00:19:23] came; it gives you all the Unix-like programmability, all the core tool that's object storage compatible, speaks native object store. But if I have to make object store look like a file system so UNIX tools would run, it would not only be inefficient, Unix tools never scaled for this kind of capacity.So, it would be a bad idea to take step backwards and bring legacy stuff back inside. For some very small case, if there are simple POSIX calls using [ObjectiveFs 00:19:49], S3Fs, and few, for legacy compatibility reasons makes sense, but in general, I would tell the community don't bring file and block. If you want file and block, leave those on virtual machines and leave that infrastructure in a silo and gradually phase them out.Corey: This episode is sponsored in part by our friends at Vultr. Spelled V-U-L-T-R because they're all about helping save money, including on things like, you know, vowels. So, what they do is they are a cloud provider that provides surprisingly high performance cloud compute at a price that—while sure they claim its better than AWS pricing—and when they say that they mean it is less money. Sure, I don't dispute that but what I find interesting is that it's predictable. They tell you in advance on a monthly basis what it's going to going to cost. They have a bunch of advanced networking features. They have nineteen global locations and scale things elastically. Not to be confused with openly, because apparently elastic and open can mean the same thing sometimes. They have had over a million users. Deployments take less that sixty seconds across twelve pre-selected operating systems. Or, if you're one of those nutters like me, you can bring your own ISO and install basically any operating system you want. Starting with pricing as low as $2.50 a month for Vultr cloud compute they have plans for developers and businesses of all sizes, except maybe Amazon, who stubbornly insists on having something to scale all on their own. Try Vultr today for free by visiting: vultr.com/screaming, and you'll receive a $100 in credit. Thats v-u-l-t-r.com slash screaming.Corey: So, my big problem, when I look at what S3 has done is in it's name because of course, naming is hard. It's, “Simple Storage Service.” The problem I have is with the word simple because over time, S3 has gotten more and more complex under the hood. It automatically tiers data the way that customers want. And integrated with things like Athena, you can now query it directly, whenever of an object appears, you can wind up automatically firing off Lambda functions and the rest.And this is increasingly looking a lot less like a place to just dump my unstructured data, and increasingly, a lot like this is sort of a database, in some respects. Now, understand my favorite database is Route 53; I have a long and storied history of misusing services as databases. Is this one of those scenarios, or is there some legitimacy to the idea of turning this into a database?AB: Actually, there is now S3 Select API that if you're storing unstructured data like CSV, JSON, Parquet, without downloading even a compressed CSV, you can actually send a SQL query into the system. IN MinIO particularly the S3 Select is [CMD 00:21:16] optimized. We can load, like, every 64k worth of CSV lines into registers and do CMD operations. It's the fastest SQL filter out there. Now, bringing these kinds of capabilities, we are just a little bit away from a database; should we do database? I would tell definitely no.The very strength of S3 API is to actually limit all the mutations, right? Particularly if you look at database, they're dealing with metadata, and querying; the biggest value they bring is indexing the metadata. But if I'm dealing with that, then I'm dealing with really small block lots of mutations, the separation of objects storage should be dealing with persistence and not mutations. Mutations are [AWS 00:21:57] problem. Separation of database work function and persistence function is where object storage got the storage right.Otherwise, it will, they will make the mistake of doing POSIX-like behavior, and then not only bringing back all those capabilities, doing IOPS intensive workloads across the HTTP, it wouldn't make sense, right? So, object storage got the API right. But now should it be a database? So, it definitely should not be a database. In fact, I actually hate the idea of Amazon yielding to the file system developers and giving a [file three 00:22:29] hierarchical namespace so they can write nice file managers.That was a terrible idea. Writing a hierarchical namespace that's also sorted, now puts tax on how the metadata is indexed and organized. The Amazon should have left the core API very simple and told them to solve these problems outside the object store. Many application developers don't need. Amazon was trying to satisfy everybody's need. Saying no to some of these file system-type, file manager-type users, what should have been the right way.But nevertheless, adding those capabilities, eventually, now you can see, S3 is no longer simple. And we had to keep that compatibility, and I hate that part. I actually don't mind compatibility, but then doing all the wrong things that Amazon is adding, now I have to add because it's compatible. I kind of hate that, right?But now going to a database would be pushing it to the whole new level. Here is the simple reason why that's a bad idea. The right way to do database—in fact, the database industry is already going in the right direction. Unstructured data, the key-value or graph, different types of data, you cannot possibly solve all that even in a single database. They are trying to be multimodal database; even they are struggling with it.You can never be a Redis, Cassandra, like, a SQL all-in-one. They tried to say that but in reality, that you will never be better than any one of those focused database solutions out there. Trying to bring that into object store will be a mistake. Instead, let the databases focus on query language implementation and query computation, and leave the persistence to object store. So, object store can still focus on storing your database segments, the table segments, but the index is still in the memory of the database.Even the index can be snapshotted once in a while to object store, but use objects store for persistence and database for query is the right architecture. And almost all the modern databases now, from Elasticsearch to [unintelligible 00:24:21] to even Kafka, like, message queue. They all have gone that route. Even Microsoft SQL Server, Teradata, Vertica, name it, Splunk, they all have gone object storage route, too. Snowflake itself is a prime example, BigQuery and all of them.That's the right way. Databases can never be consolidated. There will be many different kinds of databases. Let them specialize on GraphQL or Graph API, or key-value, or SQL. Let them handle the indexing and persistence, they cannot handle petabytes of data. That [unintelligible 00:24:51] to object store is how the industry is shaping up, and it is going in the right direction.Corey: One of the ways I learned the most about various services is by talking to customers. Every time I think I've seen something, this is amazing. This service is something I completely understand. All I have to do is talk to one more customer. And when I was doing a bill analysis project a couple of years ago, I looked into a customer's account and saw a bucket with okay, that has 280 billion objects in it—and wait was that billion with a B?And I asked them, “So, what's going on over there?” And there's, “Well, we built our own columnar database on top of S3. This may not have been the best approach.” It's, “I'm going to stop you there. With no further context, it was not, but please continue.”It's the sort of thing that would never have occurred to me to even try, do you tend to see similar—I would say they're anti-patterns, except somehow they're made to work—in some of your customer environments, as they are using the service in ways that are very different than ways encouraged or even allowed by the native object store options?AB: Yeah, when I first started seeing the database-type workloads coming on to MinIO, I was surprised, too. That was exactly my reaction. In fact, they were storing these 256k, sometimes 64k table segments because they need to index it, right, and the table segments were anywhere between 64k to 2MB. And when they started writing table segments, it was more often [IOPS-type 00:26:22] I/O pattern, then a throughput-type pattern. Throughput is an easier problem to solve, and MinIO always saturated these 100-gigabyte NVMe-type drives, they were I/O intensive, throughput optimized.When I started seeing the database workloads, I had to optimize for small-object workloads, too. We actually did all that because eventually I got convinced the right way to build a database was to actually leave the persistence out of database; they made actually a compelling argument. If historically, I thought metadata and data, data to be very big and coming to object store make sense. Metadata should be stored in a database, and that's only index page. Take any book, the index pages are only few, database can continue to run adjacent to object store, it's a clean architecture.But why would you put database itself on object store? When I saw a transactional database like MySQL, changing the [InnoDB 00:27:14] to [RocksDB 00:27:15], and making changes at that layer to write the SS tables [unintelligible 00:27:19] to MinIO, and then I was like, where do you store the memory, the journal? They said, “That will go to Kafka.” And I was like—I thought that was insane when it started. But it continued to grow and grow.Nowadays, I see most of the databases have gone to object store, but their argument is, the databases also saw explosive growth in data. And they couldn't scale the persistence part. That is where they realized that they still got very good at the indexing part that object storage would never give. There is no API to do sophisticated query of the data. You cannot peek inside the data, you can just do streaming read and write.And that is where the databases were still necessary. But databases were also growing in data. One thing that triggered this was the use case moved from data that was generated by people to now data generated by machines. Machines means applications, all kinds of devices. Now, it's like between seven billion people to a trillion devices is how the industry is changing. And this led to lots of machine-generated, semi-structured, structured data at giant scale, coming into database. The databases need to handle scale. There was no other way to solve this problem other than leaving the—[unintelligible 00:28:31] if you looking at columnar data, most of them are machine-generated data, where else would you store? If they tried to build their own object storage embedded into the database, it would make database mentally complicated. Let them focus on what they are good at: Indexing and mutations. Pull the data table segments which are immutable, mutate in memory, and then commit them back give the right mix. What you saw what's the fastest step that happened, we saw that consistently across. Now, it is actually the standard.Corey: So, you started working on this in 2014, and here we are—what is it—eight years later now, and you've just announced a Series B of $100 million dollars on a billion-dollar valuation. So, it turns out this is not just one of those things people are using for test labs; there is significant momentum behind using this. How did you get there from—because everything you're saying makes an awful lot of sense, but it feels, at least from where I sit, to be a little bit of a niche. It's a bit of an edge case that is not the common case. Obviously, I missing something because your investors are not the types of sophisticated investors who see something ridiculous and, “Yep. That's the thing we're going to go for.” There right more than they're not.AB: Yeah. The reason for that was the saw what we were set to do. In fact, these are—if you see the lead investor, Intel, they watched us grow. They came into Series A and they saw, everyday, how we operated and grew. They believed in our message.And it was actually not about object store, right? Object storage was a means for us to get into the market. When we started, our idea was, ten years from now, what will be a big problem? A lot of times, it's hard to see the future, but if you zoom out, it's hidden in plain sight.These are simple trends. Every major trend pointed to world producing more data. No one would argue with that. If I solved one important problem that everybody is suffering, I won't go wrong. And when you solve the problem, it's about building a product with fine craftsmanship, attention to details, connecting with the user, all of that standard stuff.But I picked object storage as the problem because the industry was fragmented across many different data stores, and I knew that won't be the case ten years from now. Applications are not going to adopt different APIs across different clouds, S3 to GCS to Azure Blob to HDFS to everything is incompatible. I saw that if I built a data store for persistence, industry will consolidate around S3 API. Amazon S3, when we started, it looked like they were the giant, there was only one cloud industry, it believed mono-cloud. Almost everyone was talking to me like AWS will be the world's data center.I certainly see that possibility, Amazon is capable of doing it, but my bet was the other way, that AWS S3 will be one of many solutions, but not—if it's all incompatible, it's not going to work, industry will consolidate. Our bet was, if world is producing so much data, if you build an object store that is S3 compatible, but ended up as the leading data store of the world and owned the application ecosystem, you cannot go wrong. We kept our heads low and focused on the first six years on massive adoption, build the ecosystem to a scale where we can say now our ecosystem is equal or larger than Amazon, then we are in business. We didn't focus on commercialization; we focused on convincing the industry that this is the right technology for them to use. Once they are convinced, once you solve business problems, making money is not hard because they are already sold, they are in love with the product, then convincing them to pay is not a big deal because data is so critical, central part of their business.We didn't worry about commercialization, we worried about adoption. And once we got the adoption, now customers are coming to us and they're like, “I don't want open-source license violation. I don't want data breach or data loss.” They are trying to sell to me, and it's an easy relationship game. And it's about long-term partnership with customers.And so the business started growing, accelerating. That was the reason that now is the time to fill up the gas tank and investors were quite excited about the commercial traction as well. And all the intangible, right, how big we grew in the last few years.Corey: It really is an interesting segment, that has always been something that I've mostly ignored, like, “Oh, you want to run your own? Okay, great.” I get it; some people want to cosplay as cloud providers themselves. Awesome. There's clearly a lot more to it than that, and I'm really interested to see what the future holds for you folks.AB: Yeah, I'm excited. I think end of the day, if I solve real problems, every organization is moving from compute technology-centric to data-centric, and they're all looking at data warehouse, data lake, and whatever name they give data infrastructure. Data is now the centerpiece. Software is a commodity. That's how they are looking at it. And it is translating to each of these large organizations—actually, even the mid, even startups nowadays have petabytes of data—and I see a huge potential here. The timing is perfect for us.Corey: I'm really excited to see this continue to grow. And I want to thank you for taking so much time to speak with me today. If people want to learn more, where can they find you?AB: I'm always on the community, right. Twitter and, like, I think the Slack channel, it's quite easy to reach out to me. LinkedIn. I'm always excited to talk to our users or community.Corey: And we will of course put links to this in the [show notes 00:33:58]. Thank you so much for your time. I really appreciate it.AB: Again, wonderful to be here, Corey.Corey: Anand Babu Periasamy, CEO and co-founder of MinIO. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with what starts out as an angry comment but eventually turns into you, in your position on the S3 product team, writing a thank you note to MinIO for helping validate your market.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Guest Dan Lorenc Panelists Eric Berry | Justin Dorfman | Richard Littauer Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Today, we have a very special guest, Dan Lorenc, who is a Staff Software Engineer and the lead for Google's Open Source Security Team. Dan founded projects like Minikube, Skaffold, TektonCD, and Sigstore. He blogs regularly about supply chain security and serves on the TAC for the Open SSF. Dan fill us in on how Docker fits into what he's doing at Google, he tells us about who's running the Open Standards that Docker is depending on, and what he's most excited for with Docker with standardization and in the future. We also learn a little more about a blog post he did recently and what he means by “package managers should become boring,” and he tells us how package managers can help pay maintainers to support their libraries. We learn more about his project Sigstore, and his perspective on the long-term growth of the software industry towards security and how that will change in the next five to ten years. Go ahead and download this episode now to find out much more! [00:01:09] Dan tells us his background and how he got to where he is today. [00:03:08] Eric wonders how Docker fits into what Dan is doing at Google and if he can compare Minicube and his work with what the Docker team is trying to drive. He also compares Kubernetes to Docker and how they relate. [00:06:13] Dan talks about if he sees a shift of adoption in the sphere of what he's seeing, and Eric asks if he feels that local development with Docker is devalued a little bit if you don't use the same Docker configuration for your production deploy. [00:08:49] Richard wonders in the long-term, if Dan thinks we're going to continually keep making Dockers, better Kubernetes, or at some point are we going to decide that tooling is enough. [00:10:35] We learn who's currently running the Open Standards that Docker is depending on and Dan talks about the different standards. [00:12:13] Dan shares how he thinks the shift towards open standards in particular with Docker, influences open source developers who are in more smaller companies, in SMEs, in medium-sized companies, or solo developers out there who may not have the time to get involved in open standards. [00:13:45] Find out what Dan is really excited about in terms of Docker, with standardization or in the future that will lead to a more sustainable ecosystem. [00:15:17] Justin brings up Dan's blog and a recent post he just did called, “In Defense of Package Managers,” and in it he mentions package managers should become boring, so he explains what he means by that. [00:18:01] Dan discusses how package managers can help pay maintainers to support their libraries. [00:22:03] Richard asks Dan if he has any thoughts on getting other ways of recognition to maintainers down the stack than just paying them. He mentions things that he loves that GitHub's been doing recently showing people their contribution history. [00:23:46] Find out about Dan's project Sigstore and what his adoption looks like so far. [00:26:35] Richard wonders if Dan thinks it's a good idea to have that ecosystem depend upon a few brilliant people like him doing this work or if there's a larger community of people working on security supply chain issues. Also, who are his colleagues that he bounces these ideas off of and how do we eliminate the bus factor here. Dan tells us they have a slack for Sigstore [00:30:03] We learn Dan's perspective on the long-term growth of the software industry towards security in general, how will that change over the next five to ten years, and how his role and the role of people like him will change. [00:31:35] Find out all the places you can follow Dan on the internet. Quotes [00:10:14] “You kind of move past that single point of failure and single tool shame that's actually used to manage everything.” [00:12:44] “So, they kind of helped contribute to the standardization process by proving stuff out by getting to try all the new exciting stuff.” [00:16:33] The “bullseye” release actually just went on a couple of days ago which was awesome.” [00:17:04] “It's a problem because there's nobody maintaining, which is a really good topic for sustainability.” [00:24:46] “But nobody's doing it for open source, nobody's signing their code on PyPy or Ruby Gems even though you can.” [00:29:50] “These are not the Kim Kardashians of the coding community.” [00:30:25] “Something that we've been constantly reminding, you know, the policy makers wherever we can, is that 80 to 90% of software in use today is open source.” [00:30:51] “And even if companies can do this work for the software that they produce if we don't think of, and don't take care of, and don't remember that these same requirements are going to hit opensource at the very bottom of the stack, and we're kind of placing unfunded mandates and burdens on these repositories and maintainers that they didn't sign up for it.” [00:31:11] “So we're really trying to remind everyone that as we increase these security standards, which we should do and we need to do, because software is serious, and people's lives depend on it.” Spotlight [00:32:32] Eric's spotlight is a game called Incremancer by James Gittins. [00:33:35] Justin's spotlight is Visual Studio Live Share. [00:34:04] Richard's spotlight is the BibTeX Community. [00:35:03] Dan's spotlight is the Debian maintainers. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Dan Lorenc Twitter (https://twitter.com/lorenc_dan?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Dan Lorenc Linkedin (https://www.linkedin.com/in/danlorenc) Dan Lorenc Blog (https://dlorenc.medium.com/) Tekton (https://tekton.dev/) Minikube (https://minikube.sigs.k8s.io/docs/) Skaffold (https://skaffold.dev/) Open SSF (https://openssf.org/) Open Container Initiative (https://opencontainers.org/) Committing to Cloud Native podcast-Episode 20-Taking Open Source Supply Chain Security Seriously with Dan Lorenc (https://podcast.curiefense.io/20) “In Defense of Package Managers” by Dan Lorenc (https://dlorenc.medium.com/in-defense-of-package-managers-31792111d7b1?) Open Source Insights (https://deps.dev/) GitHub repositories Nebraska users (https://github.com/search?q=location%3Anebraska&type=users) CHAOSScast podcast (https://podcast.chaoss.community/) Sigstore (https://www.sigstore.dev/) RyotaK Twitter (https://twitter.com/ryotkak) Dustin Ingram Twitter (https://twitter.com/di_codes?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Incremancer (https://incremancer.gti.nz/) Visual Studio Live Share (https://visualstudio.microsoft.com/services/live-share/) Enhanced support for citations on GitHub-Arfon Smith (https://github.blog/2021-08-19-enhanced-support-citations-github/) Debian (https://www.debian.org/) Debian “bullseye” Release (https://www.debian.org/releases/bullseye/) 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 at Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Dan Lorenc.

Install CentOS or Debian on a Raspberry Pi. I'm using CentOS, but I'll admit that Debian is the easier option by far. Do this on 3 separate Pi units, each with the same specs. Set hostnames You must have unique hostnames for each Pi. Without unique hostnames, your cluster cannot function. There are several "kinds" of hostnames, so to avoid confusion I change all of them. I use a simple naming scheme: k for "kubernetes" + an integer, starting at 100 + c for "cluster": $ sudo hostname k100c $ sudo sysctl kernel.hostname=k100c $ sudo hostnamectl set-hostname k100c $ sudo reboot Do this for each Pi. At a minimum, you end up with Pi computers named k100c, k101c, and k102c. Set verbose prompts When working with many different hosts, it's helpful to have a very verbose prompt as a constant reminder of which host you're connected to. Add this to the ~/.bashrc of each Pi: export PS1='[33[1;32m]! d t h:w n% [33[00m]' Install a Pi finder script Install an LED blinker so you can find a specific Pi when you need one. This brilliant script is by Chris Collins for his article Use this script to find a Raspberry Pi on your network, which explains how to run it. #!/bin/bash set -o errexit set -o nounset trap quit INT TERM COUNT=0 LED="/sys/class/leds/led0" if ! [ $(id -u) = 0 ]; then echo "Must be run as root." exit 1 fi if [[ ! -d $LED ]] then echo "Could not find an LED at ${LED}" echo "Perhaps try '/sys/class/leds/ACT'?" exit 1 fi function quit() { echo mmc0 >"${LED}/trigger" } echo -n "Blinking Raspberry Pi's LED - press CTRL-C to quit" echo none >"${LED}/trigger" while true do let "COUNT=COUNT+1" if [[ $COUNT -lt 30 ]] then echo 1 >"${LED}/brightness" sleep 1 echo 0 >"${LED}/brightness" sleep 1 else quit break fi done Install K3s on your control plane K3s is Kubernetes for IoT and Edge computing. It's the easiest, cleanest, and most serious method of getting Kubernetes on an ARM device. You can try other solutions (Microk8s, Minikube, OXD, and so on), but the best support comes from k3s. First, you must install k3s on one Pi. You can use any of your Pi units for this, but I use host k100c because it's the first in the sequence, so it feels logical. [k100c]$ curl -sfL https://get.k3s.io -o install_k3s.sh [k100c]$ chmod 700 install_k3s.sh Read the script to ensure that it seems to do what you expect, and then: [k100c]$ ./install_k3s.sh After installation, you're prompted to add some arguments to your bootloader. Open /boot/cmdline.txt in a text editor and add cgroup_memory=1 cgroup_enable=memory to the end of it. console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 elevator=deadline rootwait cgroup_memory=1 cgroup_enable=memory Reboot: [k100c]$ sudo reboot Once the Pi is back up, verify that your node is ready: [k100c]$ k3s kubectl get node NAME STATUS ROLES AGE k100c Ready control-plane,master 42s This Pi is the "control plane", meaning it's the Pi that you use to administer your cluster. Get the node token Obtain the control plane's node token. Thanks to k3s, this is autogenerated for you. If you not using k3s, then you must generate your own with the command kubeadm token generate. Assuming you're using k3s: $ MYTOKEN=$(sudo cat /var/lib/rancher/k3s/server/node-token) $ echo $MYTOKEN K76351a1c2497d907ba7a156028567e0ccc26b82d2174161c564152ab3add6cc3fb::server:808771e4e695e3e3465ed9a14a0581da Add your control plane hostname to your hosts file If you know how to manage local DNS settings, then you can use a DNS service to identify the hosts in your cluster. Otherwise, the easy way to make your nodes know how to find your control plane is to add the control plane's hostname and IP address to the /etc/hosts file on each node. This also assumes that your control plane has a static local IP address. For example, this is the host file of k101c and k102c: 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 10.0.1.100 k100c Verify that each host can find the control plane. For example: [k101c]$ ping -c 1 k100c || echo "fail" [k101c] Add nodes to your cluster Now you can add the other Pi computers to your cluster. On each Pi you want to turn into a computer node, install k3s with the control plane and token as environment variables. On my second Pi, for instance, I run this command: [k101c]$ curl -sfL https://get.k3s.io | K3S_URL=https://k100c:6443 K3S_TOKEN="${MYTOKEN}" sh - On my third and final Pi, I run the same command: [k102c]$ curl -sfL https://get.k3s.io | K3S_URL=https://k100c:6443 K3S_TOKEN="${MYTOKEN}" sh - Verify your cluster On your control plane, verify that all nodes are active: % k3s kubectl get nodes NAME STATUS ROLES AGE VERSION k100c Ready control-plane,master 2d23h v1.21.4+k3s1 k102c Ready 21h v1.21.4+k3s1 k101c Ready 20h v1.21.4+k3s1 It can take a few minutes for the control plane to discover all nodes, so wait a little while and try the command again if you don't see all nodes right away. You now have a Kubernetes cluster running. It isn't doing anything yet, but it's a functional Kubernetes cluster. That means you have a tiny Pi-based cloud entirely at your disposal. You can use it to learn about Kubernetes, cloud architecture, cloud-native development, and so on. Create a deployment and some pods Now that you have a Kubernetes cluster running, you can start running applications in containers. That's what Kubernetes does: it orchestrates and manages containers. You've may have heard of containers. I did an episode about Docker containers in episode 1522 of HPR, you can go listen to that if you need to catch up. I've also done an episode on LXC in episode 371 of my own show, GNU World Order. There's a sequence to launching containers within Kubernetes, a specific order you need to follow, because there are lots of moving parts and those parts have to reference each other. Generally, the hierarchy is this: namespaces are the "project spaces" of kubernetes. I cover this in great detail in my GNU World Order episode 13x39. create a deployment that manage pods. pods are groups of containers. it helps your cluster scale on demand. services are front-ends to deployments. A deployment can be running quietly in the background and it'll never see the light of day without a service pointing to it. traffic, or exposure. A service is only available to your cluster until you expose it to the outside world with an external IP address. First, create a namespace for your test application to use. [k100c]$ k3s kubectl create namespace ktest The Kubernetes project provides an example Nginx deployment definition. Read through it to get an idea of what it does. It looks something like this: apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment spec: selector: matchLabels: app: nginx replicas: 2 # tells deployment to run 2 pods matching the template template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:1.14.2 ports: - containerPort: 80 This creates metadata named nginx-deployment. It also creates a label called app, and sets it to nginx. This metadata is used as selectors for pods and services later. For now, create a deployment using the example: [k100c]$ k3s kubectl --namespace ktest create -f https://k8s.io/examples/application/deployment.yaml Confirm that the deployment has generated and started new pods: [k100c]$ k3s kubectl --namespace ktest get all 3s kubectl --namespace ktest get all NAME READY pod/nginx-deployment-66b[...] 1/1 Running pod/nginx-deployment-66b[...] 1/1 Running NAME READY deployment.apps/nginx-deployment 2/2 NAME replicaset.apps/nginx-deployment-66b6c48dd5 See the pods labelled with app: nginx: [k100c]$ k3s kubectl --namespace ktest get pods -l app=nginx NAME READY STATUS nginx-deployment-66b6c48dd5-9vgg8 1/1 Running nginx-deployment-66b6c48dd5-prgrf 1/1 Running nginx-deployment-66b6c48dd5-cqpgf 1/1 Running Create a service Now you must connect the Nginx instance with a Kubernetes Service. The selector element is set to nginx to match pods running the nginx application. Without this selector, there would be nothing to correlate your service with the pods running the application you want to serve. [k100c]$ cat

Nigel Poulton, author of The Kubernetes Book and Docker Deep Dive, discusses Kubernetes fundamentals, why Kubernetes is gaining so much momentum, deploying an example app, and why Kubernetes is considered "the" Cloud OS.

Since we last spoke about Minikube 18 months ago, the project has gone 1.0, and made large performance and usability improvements. Thomas Strömberg is the manager of the Container DevEx team at Google and a maintainer of Minikube. He talks to Craig and Adam about why system administrators are the best code reviewers, the importance of surveying users, and building bikes made of bamboo. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod Chatter of the week Baking hot Baking: Mary Berry’s Banana Loaf Caramel Slice Washington State Voters Guide Lord Buckethead Monty Python’s Election Night Special News of the week OpenSSF launched Nova from Fairwinds: monitor Helm charts for new releases Lifebelt by Gustav Westling Chaos Mesh joins the CNCF Sandbox As does the Serverless Workflow spec Announcing Vitess 7 Spinnaker Operator is GA AKS 2020-07-27 release GKE r25 Server side encryption for ECR Project report: Jaeger Episode 97 with Yuri Shkuro How Dropbox migrated from NGINX to Envoy by Alexey Ivanov and Oleg Guba Links from the interview Thomas Strömberg Minikube Episode 39, with Dan Lorenc DiRT: Disaster Recovery Testing Wheel of Misfortune Timex Sinclair ZX81 Bringing Minikube to the next Billion Users: Thomas’s talk at KubeCon China 2019 The mini Minikube Survey Other similar tools: Microk8s k3d kind Knoppix Pausing Minikube Running multiple nodes Triage Party Slow Jam Space Jam Bamboo bicycles A finished example A work in progress Thomas Strömberg on Twitter

You heard it going around, everybody is talking about Kubernetes, and Minikube, when using Docker, and CLI. It's like a foreign language! While we know Java very well, with the advent of Devops, we are supposed to be Deployers, and Scalability Experts. Well, once you start going down this episode you'll become the DevOps Hero your company was waiting for! Kubernetes is interesting because is a technology that matured almost in tandem with Docker. But Kubernetes is not Docker...Instead Kubernetes manages Docker Containers (among other things). So if you've been wondering what exactly it is? and were afraid (or just didn't know where to start), well, fear no more! We'll unveil all the Kubernetes mysteries FOLLOW US JavaPubHouse on twitter! Where we will be sharing new tech news, and tutorials! We thank DataDogHQ for sponsoring this podcast episode and providing our Guest Speaker! Don't forget to SUBSCRIBE to our cool NewsCast! Java Off Heap Kubernetes Installing Minikube Kubernetes Concepts Cloud Native Computer Foundation Do you like the episodes? Want more? Help us out! Buy us a beer! And Follow us! @javapubhouse and @fguime and @bobpaulin

Ell, Drew, Hart, and Seth talk about what Kubernetes is, how to get started with it, why and when you should use it, and more. Special Guests: Hart Hoover and Seth McCombs.

In this episode of The New Stack Makers, Williams talks to Pivotal's Cornelia Davis and Dell Technologies' William Geller about this journey to bring this majority on-board with Kubernetes, and how to use managed architecture to overcome the often overwhelming complexity of Kubernetes orchestration. Davis, VP of technology at Pivotal, pointed to MiniKube as one of the major ways to bring those people on board. “With a simple download and a couple of commands, you're on your way. You're going to be pushing apps into Kubernetes. And you're doing that on your own laptop or maybe they're doing it with one of the cloud service providers.” She continued that “And it's all so easy. It just works.”

An airhacks.fm conversation with Niklas Heidloff (@nheidloff) about: The Java Cloud Native Starter landing page www.cloud-native-starter.com, cloud native starter was tested on Kubernetes, Minikube, IBM Kubernetes Service, Minishift 3.11, OpenShift on IBM cloud, the Postgres operator, the relation between kubernetes namespace, the application and the microservices, the vue.js frontend with redux, the role of the istio ingress controller, traffic splitting and routing, backend for frontend, the MicroProfile JAX-RS client, clean architecture, fighting the Parkinson's Law of Triviality, connecting to Cloudant, and PostgreSQL via JPA, Cloudant is managed version of CouchDB, IBM offers managed DB 2 and PostgreSQL databases, Kubernetes ships without authentication and authorization, implementing the OpenID flow with NodeJS, convenient user management with Keycloak, Gatekeeper - the oauth flow implementation for Keycloak, App Identity and Access Adapter for Istio, prometheus service discovery on kubernetes, with istio you cannot look inside the application, prometheus-like monitoring with sysdig and distributed logging with logdna, traffic routing visualization with kiali, Java Cloud Native Documentation was a major effort, Jakarta EE and MicroProfile could help you to become famous, OpenLiberty with OpenJ9 and Quarkus, Niklas Heidloff on twitter: @nheidloff Niklas' blog: heidloff.net, Niklas on github: github.com/nheidloff

Tekton brings Kubernetes-style resources for declaring CI/CD-style pipelines. Kim Lewandowski is the Google Cloud product manager who recently announced it. She talks to Adam about the project while Craig sneaks in some vacation at the cafes of New Zealand. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod Chatter of the week Register for the Kubernetes Podcast from Google Cloud Live session! Craig has a lovely afternoon at the Cable Bay Cafe Auckland Kubernetes Meetup - thanks everyone! Adam reads Origin by Dan Brown Renowned Author Dan Brown, one of Craig’s favourite newspaper columns of all time News of the week Minikube releases v1.0.0 Episode 39, with Dan Lorenc Running Kubernetes locally on Linux with Minikube by Ihor Dvoretski Uber open-sources Peloton Square build a service mesh with Envoy and gRPC AWS App Mesh is GA Tetrate Q Star Trek Q The Service Mesh Era: Istio’s role in hybrid and multi-cloud by Megan O’Keefe Merging OpenTracing and OpenCensus kubectl cp vulnerability and CSI portmap vulnerability Brigade 1.0 from Deis & Microsoft Debugging an intermittent connection reset in kube-proxy by Yongkun Gui Register for the Kubernetes 1.14 webinar Meet the Ambassador: Paris Pittman Four key tips on how to do massive scale with Kubernetes by Reda Benzair Links from the interview Tekton Open Source Leadership Summit A tektōn is a Greek artisan or craftsman Formerly known as Knative Pipeline GitHub repo Triggermesh Aktion In Defense of YAML Continuous Delivery Foundation Contributing to Tekton Kim Lewandowski on Twitter

The highlights of the podcast are: Kubernetes contributes to 3 of the 7 Outcomes, (https://www.345.systems/how-we-help/) specifically Rapid Delivery, Avalilable & Scalable and Costs Optimised. We briefly cover the concept of Microservices: breaking an application into small units that are independently deployable and scalable. This reduces the complexity of our applications and reduces the regression burden as our services are isolated. Containerising applications means that your application is separated from other applications running on the same machine. Basic Kubernetes terms: Cluster: A group of machines working together to host Kubernetes. Nodes: A machine in the cluster. Master node: A machine running Kubernetes services, which control, monitor and coordinate the applications running on the cluster. Worker node: A machine that hosts applications, that has work assigned to it by the master nodes. Pod: A unit of deployment that can be one or more containers. Pods are scalable. Manifest: A file that describes how a pod should operate. Helm chart: A description of an application that spans multiple pods. We discuss configuration of a pod, notable through a ConfigMap and secrets. We look at deployment options for pods. These can be: Replicaset: Multiple copies of the same container running across the cluster. This is the typical application option. Daemonset: An instance of a worker that runs on each node. An example of this might be to collate logs. Statefulset: An instance that is aware of state. Can be used to “remember” node names and to link to persistent storage. This is how we create NoSQL database clusters in Kubernetes. We look at hosting options. In particular we call out: Amazon EKS – this is the one we typically use – hosts the master nodes and you then add your own worker nodes into the cluster. Azure AKS – equivalent to EKS and superseding Service Fabric. Workstation developers typically use Minikube to host their development version. We also talk about options for high availability by spreading clusters over multiple datacenters and regions.

Minikube is a tool that makes it easy to run Kubernetes locally, by running a single-node Kubernetes cluster inside a VM on your desktop or laptop. Craig and Adam talk to author and maintainer Dan Lorenc from Google Cloud, and in the wake of the Super Bowl, discuss how “football” means something different to each of them. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod Chatter of the week Adam watched the Super Bowl Craig watched some Superb Owls Outside the UK, you can watch them here You can watch some ads But not the ad for Blue Origin, which was pulled Snow day in Seattle! Jeff Bezos at the Super Bowl The Daily Mail is not really news Jeff Bezos’s earnings per minute News of the week Spark Operator for Kubernetes now in Beta IBM Cloud Databases report on the Operator Pattern New members in the CNCF TOC Alexis Richardson from Weaveworks Brendan Burns from Microsoft Joe Beda from VMware Matt Klein from Lyft Xiang Li from Alibaba Kelsey Hightower from Google Google Kubernetes Engine usage metering Advanced application deployments and traffic management with Istio on GKE GitHub repo Megan’s development workflow for Kubernetes Ambassador 0.5.0 API Gateways are going through an identity crisis Kubernetes as an API standard; looking toward a Rust implementation Links from the interview Dan leads a team working on: Minikube Skaffold Kaniko Knative Build Minikube was helped in the early days by Localkube from RedSpread, who were acquired by CoreOS (who were acquired by Red Hat, who were acquired by IBM) There was also Boot2docker, but Kubernetes didn’t like Docker-in-Docker much back then Guide for developing Minikube Other similar projects: Microk8s Docker Desktop Things it was hard to get working: Load balancers; solved via tunneling Persistent volume provisioning, solved with a custom hostpath provisioner Minikube Roadmap Dan Lorenc on GitHub and on the web

We’re back! This week, Mark welcomes Gabi as his new co-host! Listen in as they discuss Knative with Mark Chmarny and Ville Aikas. So what is Knative? Mark and Ville explain that Knative is basically a way to simplify Kubernetes for developers. This way, developers can focus on writing good code without worrying about all the aspects of Kubernetes, such as deploying and autoscaling. Knative helps with these functions automatically. Knative also supports many languages which allows developers to bring their own stack. The day-to-day of developing doesn’t change, which is the beautiful thing about Knative! Knative is open source and easy to deploy. Developers can find installation guides online for any Kubernetes certified instance of service. A link to the installation guide for Knative on GKE is in our show notes. Mark Chmarny Mark is a Technical Program Manager for Serverless focusing on enabling customers to be successful with our serverless portfolio on GCP, and driving community awareness of our serverless products on GKE. Prior to that Mark lead the Partner Engineering team for Data, Analytics and ML at Google. Before Google, Mark was the Sr. Director of Datacenter Solutions Group at Intel. Ville Aikas Ville is a member of the Technical Oversight Committee for Knative, leads Knative Eventing, and (with Matt) conceived ducks for K8s. Previously, Ville worked on Helm, K8s Service Catalog and Kubernetes (before it was Kubernetes). Before the OSS stint Ville was a TL for Google Cloud Storage. Cool things of the week Let the sunshine in: opening the market for more renewable energy in Asia blog Get Go-ing with Cloud Functions: Go 1.11 is now a supported language blog Building Google’s Game of the Year with Cloud Text-to-Speech and App Engine blog Welcome to the service mesh era: Introducing a new Istio blog post series blog Interview Knative site Knative Blog blog Knative on GitHub site Kubernetes site MiniKube site GKE site Pub/Sub site Cloudevents site Knative Install on Google Kubernetes Engine site Knative Slack site Question of the week How long does it take for Cloud SQL to detect an outage and trigger High Availability failover? Where can you find us next? Gabi will be discussing the awesome new features of MySQL 8.0 at PHP UK - London and you will be also able to find her at Cloud NEXT Mark will be at GDC in March, Cloud NEXT, and ECG in April Our guests will be at Cloud NEXT and KubeCon Barcelona

Melanie and Mark talk with Google Cloud’s VP of Engineering, Melody Meckfessel, this week. In her time with Google Cloud, she and her team have worked to uncover what makes developers more productive. The main focus of their work is DevOps, defined by Melody as automation around the developer workflow and culture. In other words, Melody and her team are discovering new ways for developers to interact and how those interactions can encourage their productive peak. Melody and her team have used their internal research and expanded it to collaborate with Google Cloud partners and open source projects. The sharing of research and products has created even faster innovation as Google learns from these outside projects and vice versa. In the future, Melody sees amazing engagement with the community and even better experiences with containers on GCP. She is excited to see the Go community growing and evolving as more people use it and give feedback. Melody also speaks about diversity, encouraging everyone to be open-minded and try to build diverse teams to create products that are useful for all. Melody Meckfessel Melody Meckfessel is a hands-on technology leader with more than 20 years experience building and maintaining large-scale distributed systems and solving problems at scale. As VP of Engineering, she leads the team building DevOps tools and sharing DevOps best practices across Google and with software development and operations teams around the world. Her team powers the world’s most advanced continuously delivered software, enabling development teams to turn ideas into reliable, scalable production systems. After graduating from UC Berkeley, Melody programmed for startups and enterprise companies. Since joining Google in 2004, Melody has led teams in Google’s core search systems, search quality and cluster management. Melody is passionate about making software development fast, scalable, and fun. Cool things of the week Mark is back from vacation! We are at 2 million downloads! tweet Greg Wilson twitter and github Open source gaming: Agones - 0.6.0 - site Open Match - 0.2.0 RC - site What’s new at Firebase Summit 2018 blog Interview GCP Podcast Episode 137: Next Day 1 podcast Stackdriver site GitLab site Google SRE site Borg site Cloud Spanner site Go site GKE On-Prem site Skaffold site Minikube site DORA site Cloud Build site Bazel site Question of the week If I want to configure third party notifications (such as Slack or Github) into my Cloud Build configuration - how can I do that? Sending build notifications Configuring notifications for third-party services Where can you find us next? Mark will be at KubeCon next week. Melanie will be at NeurIPS this week. She’ll be attending Queer in AI, Black in AI, and LatinX this week as well.

Kubicast Responde: Tudo o que você sempre quis saber, mas não tinha para quem perguntar.Este é um novo tipo de kubicast que estamos iniciando: o Kubicast Responde. Nele você manda suas perguntas e nós respondemos, eventualmente com você como convidado. Que tal?Neste primeiro episódio, tivemos o prazer de receber o Rodrigo Torres, SRE no vagas.com, que trouxe algumas dúvidas do seu time para compartilharmos nossa visão e experiências.Abaixo estão descritas todas as questões que foram abordadas no nosso Kubicast. Então, para saber as respostas, coloque seus fones e dê o play! :D01 — Quais as principais boas práticas que devo ter em mente ao implantar k8s?02 — Preciso entender de todo o funcionamento ou partes do k8s para poder usá-lo em produção?03 — Além da documentação do k8s, vocês indicam algum curso ou material/site para estudos?04 — Ter ambientes dedicados de test, staging e produção é viável e uma boa prática?05 — Com o Minikube, consigo explorar todas as funções onde possa ter a confiança de subir um cluster do k8s e usar em produção, ou serve apenas com uma base?06 — Devo usar k8s como serviço de algum provider, ou criar seu próprio cluster? Existe alguma regra básica?07 — Rodar Banco de Dados ou serviços, tais como RabbitMQ e Redis no k8s é aconselhável?08 —Preciso me preocupar com algum tunning nos servidores para rodar o k8s?09 — Devo usar o secrets e service discovery do próprio k8s, ou algum serviço externo, como Vault e Consul? Alguma indicação?10 — Dependendo do meu ambiente devo considerar alguns destes orquestradores?11 — Devo considerar a quantidade de containers que quero rodar em produção para usar algum destes orquestradores?12 — Devo considerar o default do k8s, ou ter um complemento de algum serviço externo, ex: Datadog?13 — Além de Istio, Traefik e Nginx, quais outras ferramentas de grande utilidade vocês indicam?Alguns Links que falamos neste episódio:Documentação Oficial — https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/katacoda — https://www.katacoda.com/courses/kubernetesPlay With Kubernetes — https://labs.play-with-k8s.com/Learn Openshift — https://learn.openshift.com/Kubernetes The Hard Way - https://github.com/kelseyhightower/kubernetes-the-hard-wayChristian Alves - Traduzido - https://github.com/cgbas/kubernetes-do-jeito-dificilFerramentas para Kubernetes:Hashicorp Vault — https://www.vaultproject.io/Hashicorp Consul — https://www.consul.io/Helm — https://helm.sh/Netflix Spinnaker — https://www.spinnaker.io/KongHQ API Gateway- https://konghq.com/Recomendações da Semana:Rodrigo: Livro MindSet e Filme Meu Pé PequenoTalita: The Imitation GameJoão: Hotel ArtemisEsperamos que você tenha gostado deste episódio, e comece a escrever suas perguntas, pois logo menos lançaremos uma enquete em

Kubernetes expert Will Boyd joins us to explain the top 3 things to know about Kubernetes, when it’s the right tool for the job, and building highly available production grade clusters. Plus the privacy improvements that could be coming to HTTPS, and a new SSH auditing tool hits the open source scene. Special Guest: Will Boyd.

In this new episode of the 10 on Tech podcast, David Davis and James Green of ActualTech Media interview Alex Chircop (@chira001) of StorageOS (@Storage_OS) about the adoption of container storage. In this interview, you’ll learn about: Why container storage is important in the industry today How the standardization around Kubernetes drives the adoption of container storage. The use case transformations companies have seen when using container storage. Resource Links: StorageOS Beta Program — https://my.storageos.com/register The Kubernetes Book By Nigel Poulton — https://www.amazon.com/Kubernetes-Book-Nigel-Poulton/dp/1521823634 MiniKube — https://kubernetes.io/docs/tasks/tools/install-minikube/ We hope you listen and enjoy, and don’t forget to subscribe to the show on iTunes, Google Play, or Stitcher!

We have the pleasure this week of having the Director of Solutions for Google Cloud Miles Ward and Cloud Solutions Architect Grace Mollison join Mark and Melanie to discuss Solution Architects, what they do and how they interact with Customers at Google Cloud Platform. Miles Ward Miles Ward is a three-time technology startup entrepreneur with a decade of experience building cloud infrastructures. Miles is Director of Solutions for Google Cloud; focused on delivering next-generation solutions to challenges in big data and analytics, application migration, infrastructure automation, and cost optimization. He worked as a core part of the Obama for America 2012 “TECH” team, crashed Twitter a few times, helped NASA stream the Curiosity Mars Rover landing, put Skype back online in a pinch, and plays a mean electric sousaphone. Grace Mollison Based in London, UK, Grace Mollison is a Cloud Solutions Architect where she helps customers to understand how to apply policies to their Google cloud platform environments as well as how to architect and deploy applications on the Google Cloud platform. In her spare time she spends time attempting to teach her international team how to speak the Queens english! Before Google Grace was a Solutions Architect at AWS where she worked with the AWS ecosystem and customers to ensure well architected solutions. Cool things of the week We have awesome new intro and outro music. Did you notice? The thing is … Cloud IoT Core is now generally available blog site JupyterLab is Ready for Users blog github Announcing Google Cloud Spanner as a Vault storage backend blog How to handle mutating JSON schemas in a streaming pipeline, with Square Enix blog FAT* livestream Interview Google Cloud Platform Solutions site Tutorials and Solutions site Machine Learning with Financial Time Series Data solution Implementing GCP Policies for Customer Use Cases solution #87 Customer Engineers with Jonathan Cham podcast Google Cloud Next Solution Architects are hiring! careers Question of the week How do I get a Docker image into Minikube without uploading it to an external registry and then downloading it all over again? Is there an easy way to do this locally? Minikube github $ docker save | (eval $(minikube docker-env) && docker load) Original references github Stack Overflow Where can you find us next? Mark will be at the Game Developer's Conference | GDC in March.

Show: 19Show Overview: Brian and Tyler talk how the Kubernetes community and technology have evolved in 2017, and make a few predictions for 2018 Show Notes:OpenShift Commons Gathering (videos): bit.ly/2BB3weVKubeCon (videos): bit.ly/2jczyn1Topic 1 - GETTING STARTED: People said that getting started w/ Docker Swarm was easier than Kubernetes. Kubernetes community created tools like Minikube & Minishift to run locally on the laptop, automation playbooks in Ansible, Katacoda have made it simple to have online tutorials, multiple cloud offerings (GKE, AKS, EKS, OpenShift Dedicated) make it simple to get a working Kubernetes cluster.Topic 2 - ENSURING PORTABILITY: Enterprise customers wants Hybrid Cloud environment. they need to understand how multiple cloud environments will impact this decision. The CNCF’s Kubernetes Conformance model is the only container-centric framework that can ensure customers that Kubernetes will be consistent between clouds.Topic 3 - INFRASTRUCTURE BREADTH: Other container orchestrators had ways to integrate storage and networking, but only Kubernetes created standards (e.g. CNI, CSI) that have gained mainstream adoption to create dozens of vendors/cloud options.Topic 4 - APPLICATION BREADTH: The community has evolved from supporting stateless apps to supporting stateful applications (and containerized storage), serverless applications, batch jobs, and custom resources definitions for vertical-specific application profiles. Topic 5 - SECURITY: There were concerns about K8S security. the community has responded with better encryption and management of secrets, and improved Kubernetes-specific container capabilities like CRI-O and OCI standardization. Topic 6 - PERFORMANCE: Red Hat (and others) have started the Performance SIG to focus on high-performance applications (HPC, Oil & Gas, HFT, etc) and profiling the required performance characteristics of these applications in containerized environments. Topic 7 - DEVELOPER EXPERIENCE: One of the themes of KubeCon was focusing on developer experience, and in just a few months we’re seeing standardization around the Helm format (for application packaging), Draft to streamline application development, Kubeapps to simplify getting started with apps from a self-service catalog. We also seen security model of non-root containers (vs. the Docker model of root-enabled containers).Topic 8 - APPLICATION EXTENSIBILITY: Kubernetes community decided not to reinvent the wheel, instead working with the Cloud Foundry Foundation to create the Open Service Broker API. Within a year, we’re now seeing implementations that have not only ported all the functionality to Kubernetes, but have extended it beyond Cloud Foundry’s previous capabilities to include support for external clouds (e.g. AWS, Azure, GCP), as well as additional services such as Ansible playbooks and other 3rd-party capabilities.Topic 9 - IMPROVING OPERATIONAL EXPERIENCE: As Clayton Coleman (Red Hat) discussed in his KubeCon keynote, companies like Red Hat are using their online environments to improve their operational experience and ultimate feed this knowledge back into the upstream products. Feedback?Email: PodCTL at gmail dot comTwitter: @PodCTL Web: http://podctl.com

Show: 4Show Description: Brian and Tyler discuss the broad range of tools that are available to deploy, operate and manage Kubernetes environments. There are lots of options...Show Notes:PodCTL #4 - TranscribedKubernetes: A Little Guide to Install OptionsMonitoring OpenShift: Three Tools for SimplificationRolling Updates to Kubernetes - At MacQuarie Bank [video]Segment 1 - [News of the Week]VMware, Google and Pivotal announced a packaged version of the Kubo project, called Pivotal Container Service (PKS). CNCF continues to be the center of Enterprise IT with VMware, Pivotal joiningSegment 2 - Why do Open Source Projects often end up with so many installers? Segment 3 - What are some of the common types of tools for kubernetes installations?Install on your laptop (e.g. Minikube, Minishift, etc.) Public Services (OpenShift Online, GKE, Azure Container Service, etc)Quickstart installer on a public cloud (e.g. Heptio, DO, kops, etc.)Kubernetes-specific installers (kubeadm, kubicorn, kargo, etc.) Deployment scripts and variations on “runbooks” (e.g. Ansible, Chef, Puppet, etc.)Segment 4 - What are some of the Day 2 tools that are used with Kubernetes?Upgrade tools (e.g. 1-click, Operators, etc.) Monitoring & Management (e.g. Prometheus, Datadog, New Relic, Zabbix, SysDig, CoScale) - https://blog.openshift.com/monitoring-openshift-three-tools/ Logging (e.g. EFK, Loggly, etc.) Application Frameworks - Save that for future shows!Feedback?Email: PodCTL at gmail dot comTwitter: @PodCTLWeb: http://podctl.com

Emmanuel, Guillaume et Antonio discutent avec Stéphanie des nouvelles du front(y compris -end). On y parle garbage collector, microprofile, javascript et même d’antivirus Windows. Enregistré le 13 juillet 2016 Téléchargement de l’épisode LesCastCodeurs-Episode–151.mp3 Stéphanie Moallic News Langages Default method et performance du code compilé Scala Go et l’amélioration de son garbage collector JMM Et tu comprends… Et tu comprends plus NPM fail encore Node.JS bridge for COBOL Belles assertions à la Spock pour Java .Net Core 1.0 releasé pour Microsoft, OS X et Linux Middleware Micro Profile Oracle est comité sur Java EE Websphere 9 compatible avec Java EE 7 Vulnérabilité Spring MVC/Security Mettre à jour Hibernate ORM dans Wildfly Vert.x 3.3 Web JWT comme une session JWT pas une session Les fonctionnalités les plus excitantes de Angular 2 Tutoriel Glide et Gaelyk JavaScript et CSS Pas besoin de Lodash/Underscore Pas besoin de JavaScript Data Neo4J JDBC driver Github archive dataset sur BigQuery Ce qu’on peut apprendre de millions de lignes de code sur Github On peut utiliser Groovy pour faire du Spark Infrastructure Kubernetes 1.3 5 days of Kubernetes 1.3 Kubernetes et autoscaling Minikube pour lancer un cluster en local AWS vs GCP Docker 1.12 inclus l’orchestration de conteneurs le résumé Docker 1.12 de Nicolas Deloof Architecture Outils et DevOps JUnit 5.0.0M1 AVG racheté et l’antivirus pour l’ordinateur de tante Christine Android Studio 2.2 M5 Divers Le pilote automatique Tesla dans un accident mortel Organisation, communication et politique Smart contracts et ses revers Un contre point sur la force des smart contracts Outils de l’épisode Windows Defender Rubrique du débutant Le garbage collector Conférences Jugsummercamp le 16 septembre JavaOne du 18–22 septembre ngEurope 25, 26 octobre 2016 Codeurs en Seine, le CfP le jeudi 24 novembre (avec des ateliers le 26 novembre) DevFest Nantes, le CfP les 9 et 10 novembre à Nantes. CfP jusqu’à fin août. Devoxx Belgique du 7 au 11 novembre Nous contacter Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/ Flattr-ez nous (dons) sur https://lescastcodeurs.com/ En savoir plus sur le sponsoring? sponsors@lescastcodeurs.com