This workshop will walk you through common scenarios that an application developer may face as they transition an application from a monolith to microservices.
The following resources need to be installed on your laptop:
- GitHub account
- Docker CLI
- Visual Studio Code
- git
- GNU Make installation:
- OSX: installation instructions using XCode or Brew
- Windows: Install WSL, then install make depending on your installed version of Linux. For example, install Make on Ubuntu.
- kubectl
- jq
- Hey - HTTP Load testing utility. A drop-in replacement for ApacheBench.
- GitHub CLI - optional
- cURL - Usually pre-installed in Unix-based Operating systems, available when using Windows with WSL installed.
- NGINX Plus trial license - You will also need to request via SalesForce to obtain an NGINX Plus certificate, private key and JWT.
- Access to F5 Distributed Cloud
You will also need to setup local authentication to GitHub.
Note: If you are taking this lab on a Windows system, it is highly recommended that you Install Linux on Windows with WSL.
At the beginning of the workshop we will walk through a common scenario that a developer might take as they transition their application from a monolith to microservices.
Start Monolith to Microservices Scenario Lab
In this lab, you will build and install the NGINX Plus Ingress Controller into your K3s cluster. You will also take a deeper look at the VirtualServer Resource and some of the common configurations a modern application might need.
In this lab, you will create an F5 Distributed Cloud Kubernetes Site using our existing K3s cluster. You will then publish the Brewz API service on the Internet without the need for a K8s ingress service.
Start F5 Distributed Cloud Kubernetes Site Lab
In this lab, you will gain a basic understanding of modern app security specs, and how to leverage them in order to secure the Brewz microservices-based application in a K8s context.