Preparation
- Deploy the Kubernetes exercise
- 1.Run the following commands:
- The exercise has been deployed successfully.
The exercise does not contain any licenses. Therefore, Airlock Microgateway runs as Community Edition
For more details see Features and support.
To run the exercise as Premium Edition, copy a valid license to .templates/microgateway/secret/microgateway.lic and execute kubectl apply -k . to re-deploy the Microgateway.
Instruction
- Change the Microgateway configuration
- 1.Connect to the website:
- ●Open the URL in your browser: https://<MINIKUBE_IP>/
- 2.Watch the logs of the Microgateway pod.
- 3.Check the following:
- ●Did Airlock Microgateway receive the request?
- ●Did Airlock Microgateway forward the request to the back-end service?
- 4.Find out the Kubernetes service name which should be protected by Microgateway.
- 5.Edit Microgateway's configuration file.
- For the mapping echoserver:
- ●backend.name
- ●backend.hosts[].name
- ●backend.hosts[].protocol
- ●backend.hosts[].port
- 6.Apply the new configuration.
- 7.Deploy the Microgateway with the new configuration.
- 8.Check the status of the Microgateway pod.
- 9.Connect to the website:
- ●Open the URL in your browser: https://<MINIKUBE_IP>/
- The web application should be reachable from the browser.
- 10.Watch the logs of the Microgateway pod.
- The log message WR-SG-SUMMARY with the key action:allowed indicates that the request has successfully proceeded.
Edit the file config/config.yaml and configure the following settings:
Use the (Microgateway) DSL reference to accomplish this task.
After modifying the configuration file, apply the new configuration by running the following command:
Cleanup
- Delete Kubernetes resources from previously exercises or solutions
- 1.Run the following commands:
- All relevant Kubernetes resources in the namespace have been deleted successfully.
copy
kubectl delete all,ing,cm,secrets,pv,pvc,sa,roles,rolebindings,clusterroles,clusterrolebindings -l purpose=microgateway-tutorial