Learn DevOps with interactive examples in this video | O'Reilly posted on the topic | LinkedIn

LinkedIn respects your privacy

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

Select Accept to consent or Reject to decline non-essential cookies for this use. You can update your choices at any time in your settings.

View organization page for O'Reilly

110,875 followers

2w

If you really want to learn something, reading isn't enough. You also need practice. This is why "Fundamentals of DevOps and Software Delivery" includes dozens of examples to try. In this video, Yevgeniy Brikman shows how "sandboxes" in the O'Reilly platform let you run the examples right in your browser, without having to install anything! Check out the book: https://lnkd.in/excgY8N6 #DevOps #Software

1 Comment

Transcript

If you really want to learn something, it's not enough to just read a book, you also need to practice whatever you read about. So, for example, if you read a book on weightlifting, it's not like you get to the very final page and suddenly you're incredibly strong. You have to spend hours at the gym practicing what you read about to actually get any kind of results. The same is true of learning just about anything else, including DevOps. That's where the book Fundamentals of DevOps and Software Delivery includes dozens and dozens of examples for you to try. This is how you're getting at the practice you need to get real results. One way you can try out these examples is to just read the book and create all of these samples locally on your own computer and run them that way. A second option is all of the example code is also available. In this GitHub repo and it's broken down by chapter. And a third option is if you're reading the book in the O'Reilly platform, you can try out the examples using sandboxes. And these make it really easy to try the examples, really easy to get the practice you need. So let me show you what those look like if you go to any chapter in the book. So let's try chapter 3. We'll go to the container orchestration section. You'll have the text over here as you might expect, and then there's this button over here that says try Sandbox. If you click on that, that'll start loading the sandbox, which will take about a minute. And when it's done, what you're going to have is on the left side, you will have the text for the book. And on the right side, you'll have a fully working development environment where you can run all of the examples without having to install anything. That's because this environment already has an interactive terminal that you'll be able to use. It has an IDE that you can use to view and edit the code. It will have all the tools installed that you need O open, Tofu, answerable, Packer, docker, all of that stuff's installed. There's even a local Kubernetes cluster ready to go. It even gives you access to an AWS account, as a lot of the examples in the book deploy into AWS. So if you scroll to the top, you'll see the AWS credentials here. You can use those to log into the console, and they're also already configured for you in the terminal itself, so you can deploy things right into AWS. So this makes it really easy to get started and to try the examples out O the terminals ready to go. I can start running commands in it, so if I run L, you can see all the example code from that GitHub repos already checked out and broken down by Charter. Since I opened up chapter 3 here, I can pop it to that folder, and since we're looking at a docker example, I can go into the docker folder. Umm, in here I can run the commands the book tells me to run to build a docker image and that'll kick that process off. If I want to see what's going on under the hood or make changes to the code, I can open U this IDE. And here's all the code. This ID, by the way, is VS Code, so it's actually pretty nice. It's running right in the browser. I can go to charter 3 to the docker folder and over here I can see I have my nodejs app which is a really simple A that responds with hello world and listens on port 8080 and that over here I have a docker file which you can use to build a docker image for the app. If I go back to the terminal you can see the image has finished building, so now I can run it using this command here. And now the A is listening on port 8080 and I can make sure that that's actually working by opening UA new terminal. Now I can run curl localhost 8080 and I get my Helloworld. So as you can see in about a minute or so, I'm able to try out these examples without having to install anything. And of course I can keep going. So for example, if you keep going through this chapter, it shows you how to deploy that same app in the local Redis cluster, so we can give that a shot. We go back to the IDE for a second and we go to the Kubernetes folder. You can see over here there's two yaml files. One of them are configures that same docker image to run in a Kubernetes cluster as a deployment with three replicas, 3 pods. And the other yaml file configures a load balancer in front of those pods to distribute traffic across them. So we can give that a shot by heading into the Kubernetes folder. We can use the apply command on each of those yaml files. There we go. If we do get pods, we can check that the A deployed, which it did. So there's my 3 odds, the three replicas. And if we get the services command. Now we can see the load balancer has deployed. There's its IP. If I curl that now I have my a running in a local Kubernetes cluster. You can see that took another method. If you keep reading this chapter, it'll show you how to deploy a Kubernetes cluster in a WS, and then you can deploy the same app in that Kubernetes cluster again without having to do anything locally, without having to set up accounts. So these sandboxes are a fantastic way to get a practice that you need so you can really learn this material. So check out the book, it's Fundamentals of DevOps and Software Delivery. Read it and then practice what you read and then you'll see really good results.

Jennifer Pollock, graphic

Jennifer Pollock

Content Strategy & Development | Product Management | Leading Innovation in Learning, Assessment & Certification

2w

To view or add a comment, sign in

More Relevant Posts

Sagar T

Senior DevOps Engineer @ Forcepoint | GitOps • K8s • Terraform • AWS | Automating delivery, scaling confidence
2w Edited
Report this post
Do you know 4 core principles of GitOps? The methodology that's revolutionizing how teams manage infrastructure and applications. 1️⃣ Declarative: Define your system's desired state using code (e.g., Kubernetes YAML). The system figures out the rest. 2️⃣ Versioned & Immutable: Git is the single source of truth. Every change is a versioned, auditable commit, making rollbacks simple and reliable. 3️⃣ Pulled Automatically: In-cluster agents automatically pull and apply changes from the Git repository, minimizing manual intervention and boosting security. 4️⃣ Continuously Reconciled: The system constantly verifies that the live state matches the desired state in Git, automatically correcting any configuration drift. Using these principles, teams can achieve faster, safer, and more consistent deployments. What has been your experience with adopting GitOps? #GitOps #DevOps #ContinuousDelivery #Kubernetes #InfrastructureAsCode #CloudNative

1 Comment
Like Comment
To view or add a comment, sign in
Taha AlOmeri

--
3w Edited
Report this post
Tired of wondering what actually gets deployed in software development? 💡 It's the Artifacts! We break down the critical role of these essential, immutable, and versioned outputs that power Continuous Delivery (CI/CD) from code to production. Artifacts are the unsung heroes of modern deployment. Learn why they are so fundamental to DevOps in this short video! 👇 ➡️ Watch now: https://lnkd.in/gyDZ2NbQ #DevOps #CI_CD #Artifacts #SoftwareEngineering #ContinuousDelivery

DevOps Demystified The Essential Role of ARTIFACTS! Explained with Examples

https://www.youtube.com/
Like Comment
To view or add a comment, sign in
Salwan Mohamed

#Platform_Engineer #Devops_Engineer #OpenShift #Kubernetes #AWS # networks #Terraform #GitOps #cisco Data_center #teamleader #Network_Atomation #ansible #ACI
6d
Report this post
Part 1 of the "GitOps Mastery: From Zero to Production Hero" Series In this first article, we’ve covered: What GitOps is and why it matters The evolution from traditional IT to GitOps Core principles and benefits Integration with Kubernetes Getting started with Argo CD Best practices and common pitfalls In the next articles, we’ll dive deeper into: Part 2: “Building Your First Production-Ready GitOps Pipeline” #Kubernetes #GitOps #DevOps #PlatformEngineering

GitOps Unveiled: Why Your Infrastructure Deserves the Git Treatment (And How to Start) medium.com
Like Comment
To view or add a comment, sign in
Venkat vineeth

Associate Software Engineer at Accenture | Aspiring DevOps Engineer| DevOps Enthusiast| Linux | AWS | Azure | Terraform | CICD | Docker | Kubernetes | Python | Shell Scripting| GitHub Actions
2w
Report this post
🚀 Day 35 - KodeKloud 100 Days Challenge 🚀 Today’s milestone: Successfully installed Docker CE and Docker Compose on CentOS! 🐳 🔧 Why Docker? Docker is the essential containerization platform that empowers developers and DevOps engineers to build, ship, and run applications consistently across environments. 🛠️ Installation Highlights: 1)Remove old versions sudo yum remove -y docker docker-client docker-common docker-latest 2) Add Docker repo sudo yum install -y yum-utils sudo yum-config-manager --add-repo https://lnkd.in/gdnCQ3U4 3) Install Docker CE and Compose plugin sudo yum install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin 4)Start and enable the Docker service sudo systemctl start docker sudo systemctl enable docker 5) Verify installation docker --version docker compose version 🌟 What this means: With Docker and Docker Compose installed, managing multi-container applications becomes effortless, boosting productivity and deployment agility. 🎯 Let's continue to push the boundaries of automation and container orchestration! 💪🔥 #Docker #DockerCompose #DevOps #KodeKloud #100DaysOfCode #Containers #CentOS #Automation #CloudNative
Like Comment
To view or add a comment, sign in
Hans de Waal

Founder at Arero7 | Inventor of the Unified Data Field (UDF) | Data & AI Transformation Leader | Architect of Digital Frameworks that turn Strategy into Execution
3w
Report this post
🚀 Great software starts long before the first line of code. 🔍 See the whole picture: understand processes, domains, and future scale. 🏗️ Design the architecture: keep it lean, but solid. ⚙️ Implement the essentials: no unnecessary setup. 🔄 Integrate Git + CI/CD: ensure smooth collaboration and reliable delivery. Because without a strong foundation, scaling becomes chaos. 👉 How do you make sure your software stays simple and scalable? #SoftwareArchitecture #ScalableDesign #DevOps #CICD #TechLeadership #Innovation #Arero7
Like Comment
To view or add a comment, sign in
Ons MOKNI

DevOps & Data Analytics Specialist | Microsoft PL-300 Certified
3d
Report this post
⚓ How the Game changed ? Lest's see 🚀 Traditional pipelines deploy software. But #Kubernetes delivers resilience, speed, and trust. 🔹 Consistent Builds Every environment runs exactly the same — no “works on my machine.” 🔹 Zero-Downtime Deployments Blue-Green, Canary, Progressive — Kubernetes automates them all. 🔹 Self-Healing Infrastructure Pods crash? Kubernetes restarts them. Automatically. 🔹 Smarter Pipelines Tools like ArgoCD & Jenkins integrate directly with the Kubernetes API — your delivery becomes declarative and automated. 💡 With Kubernetes, CI/CD isn’t just about delivery. It’s about continuous confidence. ⭕️ Faster feedback loops ⭕️Safer releases ⭕️Happier teams 🌍 In 2025, cloud-native CI/CD = Kubernetes. 💚 I ❤️ DevOps | 💙 I 💚 Kubernetes #DevOps #CICD #GitOps #CloudNative #Automation #ContinuousDelivery #ContinuousInnovation
Like Comment
To view or add a comment, sign in
Vaishnavi K

Sr Site Reliability Engineer | DevOps Engineer | Cloud Engineer | AWS | GCP | AZURE | CI/CD | Kubernetes | Containerization
2w
Report this post
Infrastructure as Code: The DevOps Superpower Before IaC, provisioning infrastructure meant manual steps, endless tickets, and “it works on my machine” headaches. Now, with tools like Terraform, CloudFormation, and Ansible, we can: ✅ Define infrastructure in code → version control with Git ✅ Automate deployments → consistent environments ✅ Scale and rebuild infrastructure in minutes, not days ✅ Enable true DevOps collaboration between devs & ops 👉 IaC is more than automation. It’s about treating infrastructure like software—tested, reviewed, and reproducible. 💡 My rule: If it isn’t in code, it doesn’t exist. Do you already use IaC in your projects? If yes, which tool do you prefer—Terraform, Ansible, or CloudFormation? #DevOps #InfrastructureAsCode #Terraform #Automation #CloudEngineering
Like Comment
To view or add a comment, sign in
Ashish Chakrabortty

Sr. Product Marketing Manager
3w
Report this post
Sysdig's 𝗚𝗿𝗮𝗻𝗱 𝗔𝘁𝗹𝗮𝘀 𝗼𝗳 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 outlines how teams can build protection into every stage of #DevOps - from code and CI/CD to registries and runtime Explore the guide: https://okt.to/DPnOJo
Like Comment
To view or add a comment, sign in
Sainithin Sindhe D

Site Reliability Engineer @ Best Buy | AWS, GCP, Azure | Jenkins, Terraform, Docker, Kubernetes | Linux, Bash, Python | GitHub Actions, Ansible | Prometheus, Grafana | Nexus, SonarQube
3w
Report this post
👉 Ever wondered how to deploy new code safely and efficiently? It all comes down to choosing the right Kubernetes deployment strategy! This visual breakdown covers essential approaches like: Canary: Gradually testing updates with real users. Blue-Green: Instant rollbacks with zero downtime. A/B Testing: Experimenting with features and gathering user feedback. Rolling Update: Continuous updates without service interruption. Recreate: Simple but with downtime. Shadow: Testing under real workloads without user impact. Each comes with its own trade-offs, ensuring you can pick the best fit for your application's needs. Which strategy is your go-to? Share your experiences below! #Kubernetes #K8s #DevOps #Deployment #CloudComputing #Containerization #SoftwareEngineering #TechInsights #SystemDesign #ITOperations #ReleaseManagement #CanaryDeployment #BlueGreenDeployment #RollingUpdate #ABTesting
Like Comment
To view or add a comment, sign in
Abdelkarim Oucif

Software Engineer & Full-Stack Developer | Ph.D. student in AI | Building Scalable, Efficient Systems
2w
Report this post
I’ve spent the last few days getting hands-on with DevOps concepts, testing how Docker, Kubernetes, and automation tools work together in real setups. I built a collection of small, practical examples and organized them in this repository. It contains a set of examples where I applied different DevOps concepts: * Containerization using Docker and Docker Compose. * Load balancing & reverse proxy with Nginx image. * Orchestration through Docker Swarm and Kubernetes. * Configuration & secrets management using ConfigMaps and Secrets. * Persistent storage with Kubernetes persistent volumes and claims components. * Full app deployment: a simple CRUD app running on Kubernetes, with: - Deployments and Services for frontend, backend, and database. - Secrets for sensitive environment variables. - ConfigMaps for shared app configuration. - Persistent Volumes & Claims for Postgres database storage. - Ingress routing through Nginx for local domain access (like notes.local). If you’re also exploring DevOps or Containerization tools, maybe this repo can help you get some insights. And if you’ve been working with Docker or Kubernetes for a while, I’d really appreciate your feedback or suggestions on how to improve it. Also, feel free to fork, improve, or suggest new examples! #DevOps #Docker #Kubernetes #Containerization #LearningByDoing #OpenSource #Automation https://bit.ly/4o4kNAK

GitHub - okarimo17/dev-ops: Applying dev-ops, docker, k8s... github.com

2 Comments
Like Comment
To view or add a comment, sign in

O'Reilly

110,875 followers

View Profile Connect

Explore content categories