How to Configure AWS Application Loadbalancer (ALB) for Veeam Kasten for Kubernetes

secrets:
#to configure AWS keys for direct integration if the in-tree provisioner is used as a provisioner in storageClass
  awsAccessKeyId: XXXXXXXXXXX
  awsSecretAccessKey: **SECRET**
auth:
#Enabling external access to K10 using ingress required authentication to be enabled. Enabled token auth for simplicity
  tokenAuth:
     enabled: true
ingress:
  create: true
  host: k10.example.kasten.io
#setting this path type to prefix will set the listener rules to allow the paths with the prefix k10/*
  pathType: Prefix
  annotations:
#AWS Load Balancer Controller supports the following traffic modes.
#instance mode- Registers nodes within your cluster as targets for the ALB. Traffic reaching the ALB is routed to NodePort for your service and then proxied to your pods
#ip mode - Registers pods as targets for the ALB. Traffic reaching the ALB is directly routed to pods for your service.
     alb.ingress.kubernetes.io/target-type: ip
#scheme can be internal or internet-facing
     alb.ingress.kubernetes.io/scheme: internet-facing
#By default, the success code is 200, but you can optionally specify additional success codes for redirects while configuring health checks.
     alb.ingress.kubernetes.io/success-codes: 200,302,303
#path to perform loadbalancer healthchecks. K10s gateway by default uses /k10/ path(this changes based on the helm release name that is used for installing k10)
     alb.ingress.kubernetes.io/healthcheck-path: /k10/
#annotation to let the ALB ingress controller know that it needs to provision an ALB loadbalancer.
     kubernetes.io/ingress.class: alb
#To share an application load balancer across multiple service resources using IngressGroups
#To join an ingress to a group, add the following annotation to a Kubernetes ingress resource specification.
    #alb.ingress.kubernetes.io/group.name: my-group

helm install k10 kasten/k10 --create-namespace --namespace=kasten-io -f k10values.yaml