DevOps Labs: 12 Real DevSecOps projects

Install Docker Desktop on Windows, which includes Docker Compose, by downloading the official exe and following a straightforward install.

Install Oracle VirtualBox on Windows for the labs by downloading the VirtualBox binaries and launching the Oracle VM VirtualBox manager; ensure your computer has ample memory and a fast CPU.

Install vagrant on windows by setting up docker and virtualbox, download the windows package, run the installer in PowerShell as administrator, and follow hyper-v compatibility steps.

Demonstrates running vagrant on windows using a provided vagrant file, starting the ubuntu image with vagrant up via the virtualbox provider, and accessing via vagrant ssh.

Install Chocolatey on Windows to manage packages and install useful tools, following the steps at chocolate.org/install; this Windows package manager, like npm or maven, supports practical practice.

Demonstrate installing Helm on Windows by running PowerShell as administrator, with a straightforward local Kubernetes setup for hands-on practice.

Install minikube on Windows for Kubernetes testing, following provided download links and installation instructions. Use PowerShell as a straightforward setup method and refer to the URL for current guidance.

Finish installing minikube and install kubectl via minikube on Windows, verify the kubectl version, and proceed to the next step.

Create a read-only kubeconfig file to grant Kubernetes access with restricted permissions for non-admin users.

This lab uses canned instead of mini cube, installs the cube control and canned, and walks through creating a cluster; preparation may take a while, so pause and resume later.

verify the control plane, deploy the index, and create a read only kubeconfig file from a service account using git bash.

Create a read-only kubeconfig context to enforce permissions, verify a node, and demonstrate that forbidden errors prevent deleting or creating objects in Kubernetes.

Learn to deploy a helm chart with a cron job that backs up the vault to MinIO storage, using Docker for Windows and Minikube for orchestration.

Learners set up a local Kubernetes environment with Minikube and verify the cluster using kubectl. They install Helm and use the dashboard to troubleshoot during the step-by-step lab.

Install the backup vault manually using the helm chart, copy and run the commands, and note the root user, root password, and version 5.0.5 for future steps.

Install the volt helm chart, create separate namespaces, and verify the deployment status until the container is running, preparing the backup vault in MinIO for the next steps.

Perform the initial vote setup for the backup vault in MinIO by copying and pasting commands, preparing keys, and logging in with a token.

Log in to the designated port, run and copy commands to back up data, capture the row ID and secret ID, and update the config file for the Minio vault.

Learn to update vault backup values.yaml by syncing raw ID and secret ID, verify them, and upload a config map to complete the backup workflow in Minio.

explore a public MinIO playground at play.min.io:9443, create a brands bucket with test files, and work through troubleshooting steps to learn DevSecOps lab concepts and backup vault in MinIO.

Verify minikube status, install capacitor, and run verification commands in git bash to progress with a Java app in Kubernetes for monitoring config map modifications.

Develop a Java application that uses the Kubernetes API to modify a file mounted by a ConfigMap and monitor live updates as changes propagate.

Install minikube and helm to enable a live home deployment in Kubernetes, start minikube, and complete the prerequisites before pausing for the next video.

Minikube started; use the status command and download the kube controller and kubectl. The Minikube dashboard is handy as we anticipate seeing the node in the next video.

Add the hab report repository and run the setup command, install Jenkins, and configure stream logging to proceed to the next video.

Learn how to install Jenkins in Kubernetes, monitor readiness with port forward, initialize, retrieve the admin password, and access the Jenkins dashboard for post-install insights.

Troubleshoot intermittent Jenkins pipeline issues caused by a changing plugin; update the plugin text txt with new values and rerun docker compose to resolve the error.

Open a new command window and initiate the vote. Unseal Vault by using three keys to unlock from sealed state and proceed to the next step.

Log in with the root user using the token, then enable the world key v6 engine version 2, read data, and create a vote policy, role, and secret ID.

Complete the final steps of the vote by providing the required values for Jenkins and proceed to the next step with the gathered information.

Configure vault credentials in a Jenkins pipeline by logging in with a dot env file and adding system global credentials with raw ID and secret ID.

Generate a GitHub personal access token (classic token) in developer settings, copy the token, and prepare credentials for the next lab.

Establish secure credential management in a vault Jenkins pipeline by creating a second credential using a GitHub username and its token, then label and describe it for the next step.

Configure and run a Jenkins pipeline from SCM git, set repository URL, credentials, main branch, and script path, then build to a green, successful result.