Redirect Amazon EKS traffic to Managed AIRS resource

1. Download the Helm charts from the Resource page under the Managed AIRS section.
2. Locate and open the values.yaml file within the downloaded Helm folder structure.
3. Edit the values.yaml file to match your firewall deployment.

   In values.yaml, populate the endpoints field as a list — one entry per Availability Zone where your EKS cluster has active nodes. Each entry requires two fields: address (the private IP of the GWLBE ENI in that Availability Zone) and zone (the exact Availability Zone name matching where your nodes run).

   Single Availability Zone deployment:

   endpoints:
     - address: 10.2.23.80
       zone: us-west-2b

   Multi-Availability Zone deployment (one GWLBE ENI per Availability Zone):

   endpoints:
     - address: 10.2.23.80
       zone: us-west-2b
     - address: 10.2.15.42
       zone: us-west-2a
     - address: 10.2.31.19
       zone: us-west-2c

4. Update the ClusterID field with a unique identifier for your cluster.
5. Validate your changes:

   • All endpoint IP addresses are valid private IP addresses.
   • All Availability Zones match the zones where your EKS cluster has nodes.
   • The namespace exists in your Kubernetes cluster.
   • The cluster ID is within the valid range of 1 to 2048.
6. Save the file and run helm install from your local system configured to access the targeted Amazon EKS cluster.

   The Helm script deploys the PAN CNI daemonset to run natively across all active worker nodes in the cluster.