Azure deployment

This document describes a recommended step-by-step guidance for deploying the AppScan 360° application to Azure Kubernetes Service (AKS). It covers infrastructure components, storage for persistent volumes, database options, container registry, certificate management, ingress/gateway patterns.

Azure infrastructure requirements

The table below provides an overview of the Azure services necessary for AppScan 360°, along with the standard reference deployment and supported alternatives.

Please refer to the Resource Requirements and Prerequisites Setup Guide for AppScan 360° application installation.

AppScan 360 Requirement Recommended/ Reference Deployment Azure Options Notes
Kubernetes Platform Azure Kubernetes Service (AKS)^ Standard_D16s_v5 Any supported Kubernetes platform AKS recommended for Azure deployments
Database Azure SQL Database Azure SQL Managed Instance, SQL Server on Azure VM, Azure Database for PostgreSQL Microsoft SQL Server or PostGreSQL required
Shared Storage# Azure Blob CSI Driver Azure Files Premium CSI, Azure NetApp Files, Enterprise NFS Must support ReadWriteMany (RWX)
Certificate Management cert-manager Enterprise PKI TLS certificates required
Container Registry Harbour (hclcr.io) Any OCI-compliant registry Registry must be reachable from AKS
Ingress Kubernetes Gateway API Azure Application Gateway, Azure Front Door Customer architectural decision

Important Note:-

Node Optimization: To ensure uninterrupted concurrent dynamic analysis (DAST) for AppScan 360°, the underlying Linux kernel on the AKS worker nodes must be configured with elevated `inotify` resource limits. Integrate the following kernel parameter into the node deployment scripts or initialization configurations to safeguard against pod exhaustion errors:

`fs.inotify.max_user_instances=524288`

Azure infrastructure preparation

Ensure that all required Azure infrastructure resources are fully provisioned prior to initiating the AppScan 360° deployment.

Prerequisite infrastructure checklist

Azure Resource Required Status / Verification
Azure Subscription Active and accessible
Resource Group Successfully provisioned
AKS Cluster kubectl connectivity confirmed
SQL Server Database connection verified
Shared Storage RWX StorageClass configured
Container Registry Image pull and push capabilities validated
DNS Hostname mapping pre-planned
TLS Certificates Valid and available

Pre-deployment validation

Prior to commencing deployment, ensure the following cluster parameters are verified:

  • Established kubectl connectivity
  • Operational worker nodes in "Ready" status
  • Healthy CoreDNS deployment
  • Fully functional cluster networking

To align with your organization's security architecture and policy, utilize private networking configurations where possible and strictly limit exposure to components.

Kubernetes cluster preparation

Prior to deploying AppScan 360°, the underlying Kubernetes cluster must be properly configured and verified according to the following baseline requirements.

Infrastructure Component Functional Purpose Verification Criteria
Target Namespace Resource isolation specifically for AppScan 360 workloads Namespace provisioned
cert-manager Automated lifecycle management of TLS certificates All pods operational
Gateway API Management of application ingress routing Gateway status Ready
Kubernetes Secrets Secure storage for SQL database, image registry, and application credentials Secrets successfully created
Storage Class Provisioning of shared persistent volumes RWX capability validated

Deploying AppScan 360°

To perform the deployment of AppScan 360° on AKS, utilize the official Helm chart provided alongside the product release.

For release-specific configurations, parameters, and deployment commands, please refer to theAppScan 360° Helm Installation Guide.

Pre-Deployment Validation

Infrastructure / Application Component Expected Operational Status
Application Login Page Accessible
HTTPRoute Accepted
Gateway Ready
PVC Bound
Services Available
Deployments Available
Pods Running