lab:kubernetes_app:review
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
lab:kubernetes_app:review [2024/04/08 02:08] – added sqlmap user | lab:kubernetes_app:review [2024/05/13 18:15] (current) – removed user | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Review ====== | ||
- | Congratulations! You successfully completed a WHOLE lot of automation! | ||
- | * Installed and configured Oracle VirtualBox using Ansible | ||
- | * Deployed a fleet of auto-installed virtual Ubuntu servers | ||
- | * Provisioned Kubernetes on these servers | ||
- | * Deployed a MySQL service | ||
- | * Deployed a demonstration web application that consumes the MySQL service | ||
- | There are clearly things to consider to deploy an actual production web application. Here are a few things you can experiment with: | ||
- | * create a playbook to bring the environment back up when the host reboots | ||
- | * use of Kubernetes secrets instead of environment variables to configure the MySQL root password | ||
- | * configure a Nginx virtual system for [[https:// | ||
- | * fork your own demo application and add https support | ||
- | * Prometheus Node Exporter: explore metrics at the node (system) level; relatively easy to set up, it exposes useful metrics about host machine resources | ||
- | * CI/CD Pipelines: Investigate a simple pipeline (Jenkins, GitLab CI, etc) to automate building a container image for your web app and trigger Deployments when code changes. | ||
- | |||
- | ====== Learn More ====== | ||
- | Learn more by installing sqlmap and scan the test application for vulnerabilities. | ||
- | |||
- | ====== Next Step ====== | ||
- | You have reached the end of this lab. | ||
- | |||
- | To clean up the environment from your host: | ||
- | < | ||
- | |||
- | Or back to [[Step 6 - Application Configuration]] or [[Start]] |
lab/kubernetes_app/review.1712542090.txt.gz · Last modified: 2024/04/08 02:08 by user