![10.3.3 testout lab 10.3.3 testout lab](https://cdn.shopify.com/s/files/1/0791/7731/files/NetworkSS3.jpg)
10.3.3 TESTOUT LAB SOFTWARE
DevOpsĪ hands-on DevOps course covering the culture, methods and repeated practices of modern software development involving Vagrant, VirtualBox, Ansible, Kubernetes, k3s, k3d, Traefik, Docker, Taiga, GitLab, Drone CI, SonarQube, Selenium, InSpec, Heimdall 2, Arch Linux.Ī reveal.js presentation written to accompany this course can found at.
![10.3.3 testout lab 10.3.3 testout lab](https://www.coursehero.com/thumb/99/f5/99f57ab4600cd6ff231219b2e7a7fc20c8a43a3f_180.jpg)
This new version of my class infrastructure-as-code automation focuses instead of directly configuring the host or if need be a single Vagrant for the purpose of development. Around this same time I also moved fully off my MacBook for personal development moving to Arch Linux where I used Docker. Around this same time I was considering using k3d I also gave Docker Desktop's means of providing a Kubernetes cluster a try but I found it lacking, so I stuck with k3d. K3d is a lightweight wrapper to run k3s in Docker and provides a rather elegant solution to create and manage a single or multi-node k3s cluster for development vice standing up multi-VMs and the burden they impose on the host (in my case my laptop). The Kubernetes cluster my class used made use of was k3s and as it matured k3d was introduced. The approach modeled how I pre-flighted my work on my laptop vice using minikube. Several Vagrants were created through automation to run a multi-node Kubernetes cluster as well asa development VM. The prior version relied on multiple Vagrants (i.e., virtual machines) and was a beast to maintain. This newest version of my Hands-on DevOps class is a re-platforming of sorts - A sort of rewrite if you will. The content of this course is actively under development whereas the prior is not. This is the second edition of my hands-on DevOps course building upon nemonik/hands-on-DevOps.