Anonymizing Using Azure Kubernetes Service (AKS) on

Set up Protegrity Anonymization API on Azure Kubernetes Service (AKS)

Mon, 01 Jan 0001 00:00:00 +0000

To set up and use the Protegrity Anonymization API on Azure, follow the steps provided in this section.

Preparing the Base Machine
Creating a Kubernetes Cluster
Accessing the Cluster
Use the following link to upload the Docker image to the Azure container registry (ACR) for running the Protegrity Anonymization API in AKS.
Uploading the Image to the Azure Container Registry
Complete the steps provided in the following link to create an Azure disk and obtain the subscription ID.
Creating an Azure Disk

Preparing the Base Machine

Mon, 01 Jan 0001 00:00:00 +0000

Install the Azure CLI and log in to your account to work with Protegrity Anonymization API on the Azure Cloud.

Install and initialize the Azure CLI on your system.

For more information about the installation steps, refer to How to install the Azure CLI.
Log in to your account using the following command from a command prompt.
```
az login
```

The configuration complete message appears.

{
 "cloudName": "AzureCloud",
 "homeTenantId": 
 "id":
 "isDefault": true,
 "managedByTenants": [
 {
 "tenantId":
 }
 ],
 "name": "Azure Cloud Platform",
 "state": "Enabled",
 "tenantId": 
 "user": {
 "name":
 "type": "user"
 }
}

Install Kubectl version 1.34, which is the command line interface for Kubernetes.

Creating a Kubernetes Cluster

Mon, 01 Jan 0001 00:00:00 +0000

This section describes how to create a Kubernetes Cluster on Azure.

Note: The steps listed in this procedure for creating a Kubernetes cluster are for reference use. If you have an existing Kubernetes cluster or want to create a Kubernetes cluster based on your own requirements, then you can directly navigate to the section Accessing the AKS Cluster to connect your Kubernetes cluster and the Linux instance.

To create a Kubernetes cluster:

Accessing the AKS Cluster

Mon, 01 Jan 0001 00:00:00 +0000

Connect to the cloud service using the steps in this section.

Log in to the Linux instance and run the following command to connect your Base machine to the Kubernetes cluster.
```
az aks get-credentials --resource-group <Name_of _Resource_group> --name <Name_of Kubernetes_Cluster>
```
The Base machine is now connected with the Kubernetes cluster. You can now run commands using the Kubernetes command line interface (kubectl) to control the nodes on the Kubernetes cluster.

Uploading the Image to the Azure Container Registry

Mon, 01 Jan 0001 00:00:00 +0000

Use the information in this section to upload the Docker image to the Azure Container Registry (ACR) for running the Protegrity Anonymization API in AKS.

Note: For more information about creating the Azure Container Registry, refer to Create an Azure container registry using the Azure portal.

To install the Protegrity Anonymization API:

Log in to the machine as an administrator to install the Protegrity Anonymization API.
Install Docker using the steps provided at https://docs.docker.com/engine/install/.

Setting up NGINX Ingress Controller

Mon, 01 Jan 0001 00:00:00 +0000

Complete the steps provided here for installing the NGINX Ingress Controller on the base machine.

Login to the base machine and open a command prompt.
Create a namespace where the NGINX Ingress Controller needs to be deployed using the following command.
```
kubectl create namespace <Namespace name>
```
For example,
```
kubectl create namespace nginx
```
Add the repository from where the Helm charts for installing the NGINX Ingress Controller must be fetched using the following command.

Using Custom Certificates in Ingress

Mon, 01 Jan 0001 00:00:00 +0000

Protegrity Anonymization API uses certificates for secure communication with the client. You can use the certificates provided by Protegrity or use your own certificates. Complete the configurations provided in this section to use your custom certificates with the Ingress Controller.

Ensure that the certificates and keys are in the .pem format.

Note: Skip the steps provided in this section if you want to use the default Protegrity certificates for the Protegrity Anonymization API.

Updating the Configuration Files

Mon, 01 Jan 0001 00:00:00 +0000

Use the template files provided to specify the AKS settings for the Protegrity Anonymization API.

Create the Protegrity Anonymization API namespace using the following command.
```
kubectl create namespace <name>
```
Note: Update and use the from the values.yaml file that is present in the Helm chart.
Extract and update the files in the ANON-API_HELM_1.4.1.14.tgz package.

The ANON-API_HELM_1.4.1.14.tgz package contains the values.yaml file that must be modified as per your requirements. It also contains the templates directory with yaml files.

Deploying the Protegrity Anonymization API to the AKS Cluster

Mon, 01 Jan 0001 00:00:00 +0000

Deploy the pods using the steps in the following section.

Run the following command to deploy the pods.

helm install <helm-name> /<path_to_helm> -n <namespace>

Verify that the necessary pods and services are configured and running.
1. Run the following command to verify the information for accessing the Protegrity Anonymization API externally on the cluster. The port mapping for accessing the UI is displayed after running the command.
```
kubectl get service -n <namespace>
```
2. Run the following command to verify the deployment.

Viewing Protegrity Anonymization API Using REST

Mon, 01 Jan 0001 00:00:00 +0000

Use the URLs provided here for viewing the Protegrity Anonymization API service and pod details after you have successfully deployed the Protegrity Anonymization API.

You need to map the IP address of Ingress in the hosts file with the host name set in the Ingress configuration.

For more information about updating the hosts file, refer to step 2 of the section Enabling Custom Certificates From SDK.

Open a web browser.
Use the following URL to view basic information about the Protegrity Anonymization API.