Follow this guide to deploy and configure Airlock Microgateway using kubectl.
Prerequisites
- Kubernetes cluster
- Install kubectl
- Install curl
In case no Kubernetes cluster is available, use Minikube to deploy Airlock Microgateway and getting used to it.
Deployment
Follow the instructions below to deploy Airlock Microgateway with an echo and a Redis service.
- Manifest files for Airlock Microgateway
- Create the folder
getting_started/
. - Create the file
microgateway-config.yaml
in the folder getting_started/, which contains the ConfigMap with the Airlock Microgateway configuration: - Follow the instructions below to create the file
microgateway-secret.yaml
in the folder getting_started/. - For the premium edition, do the following:
- Copy the Microgateway license file to
getting_started/microgateway.lic
. - Run the following command:
- For the community edition, do the following:
- Run the following command:
- Create the file
microgateway-deployment.yaml
in the folder getting_started/, which contains the Deployment definition for Airlock Microgateway: - Create the file
microgateway-service.yaml
in the folder getting_started/, which contains the Service definition for Airlock Microgateway:
Create the file microgateway.passphrase
in the folder getting_started/, which contains the passphrase for encryption.
The content of the license file looks like:
-----BEGIN LICENSE----- eJxFkEuzokgUhP+LWyeCAgqRjugFLwURhAvycJgFaAkFWLxBuNH/vY1eTC/z ... ... ... -----END LICENSE-----
- Manifest file for Redis
- Create the file
redis.yaml
in the folder getting_started/, which contains all resource definitions for Redis:
- Manifest file for the echo server
- Create the file
echo.yaml
in the folder getting_started/, which contains all resource definitions for the echo server:
- Manifest file for Ingress
- Create the file
ingress.yaml
in the folder getting_started/, which contains the definition for the Ingress controller:
- Deploy the Kubernetes resources
- Run the following command to the deploy the Kubernetes resources:
Verification
Follow the instructions below to verify that the Helm release could be deployed successfully.
- Check the status of the pods:
- Send a curl request to the echo server:
- The request is sent to the echo server.
- The Airlock Microgateway logs show, that the request has been filtered by Microgateway.
All pods have a STATUS
of Running
.
In case that Airlock Microgateway was not deployed in Minikube, replace the part $(minikube ip)
with the IP address of the Ingress of your Kubernetes cluster.
Uninstall
Follow the instructions below to uninstall the deployment.
- Uninstall the deployment