AWS Gov Cloud support (#421)

AWS Gov Cloud support - updated readme & addon values yaml for aws-load-balancer-controller addon

charts/addons/README.md

@@ -61,16 +61,32 @@ Configuration   | Usage
 `clusterName`   | The name of your EKS cluster.  Resources created by the ALB Ingress controller will be prefixed with this string.
 `region`     | AWS region of the EKS cluster. Required if if ec2metadata is unavailable from the controller Pod.
 `vpcId`      | VPC ID of EKS cluster, required if ec2metadata is unavailable from controller pod.
+`image.repository`  | Your Amazon EKS Amazon ECR image repository, which is required for AWS GovCloud (US) deployments.
 `serviceAccount.annotations`  | Annotate the service account with `eks.amazonaws.com/role-arn` IAM Role that provides access to AWS resources.
 
 Example:
 
+
+For Commercial Cloud Deployment:
+```yaml
+aws-load-balancer-controller:
+  enabled: true
+  clusterName: "YOUR_EKS_CLUSTER_NAME"
+  region: "YOUR_EKS_CLUSTER_REGION"
+  vpcId: "YOUR_EKS_CLUSTER_VPC_ID"
+  serviceAccount:
+    annotations:
+      eks.amazonaws.com/role-arn: "YOUR_IAM_ROLE_ARN"
+```
+For AWS Gov Cloud Deployment:
 ```yaml
 aws-load-balancer-controller:
   enabled: true
   clusterName: "YOUR_EKS_CLUSTER_NAME"
   region: "YOUR_EKS_CLUSTER_REGION"
   vpcId: "YOUR_EKS_CLUSTER_VPC_ID"
+  image:
+    repository: "Amazon EKS Amazon ECR image repository"
   serviceAccount:
     annotations:
       eks.amazonaws.com/role-arn: "YOUR_IAM_ROLE_ARN"

charts/addons/values.yaml

@@ -44,6 +44,7 @@ traefik:
       memory: 500Mi
 
 # When deploying on AWS EKS, set this to true to install aws-load-balancer-controller.
+## For more details on this, please refer https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html
 aws-load-balancer-controller:
   enabled: false
   ## Resources created by the ALB Ingress controller will be prefixed with this string
@@ -52,6 +53,10 @@ aws-load-balancer-controller:
   region: "YOUR_EKS_CLUSTER_REGION"
   ## VPC ID of k8s cluster, required if ec2metadata is unavailable from controller pod
   vpcId: "YOUR_EKS_CLUSTER_VPC_ID"
+  ## Deployments on AWS Gov Cloud requires the image repository to be passed explicitly. Please enable this block for aws gov cloud deployments only.
+  ## The AMAZON_CONTAINER_IMAGE_REGISTRY can be found here: https://docs.aws.amazon.com/eks/latest/userguide/add-ons-images.html
+  ## image:
+  ##  repository: "<AMAZON_CONTAINER_IMAGE_REGISTRY>/amazon/aws-load-balancer-controller"
   ## To create IAM Role, see https://docs.aws.amazon.com/eks/latest/userguide/create-service-account-iam-policy-and-role.html#create-service-account-iam-role
   ## Create policy with https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/main/docs/install/iam_policy.json and
   ## attach it to the role. See, https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller for more details

docs/Deploying-Pega-on-EKS.md

@@ -434,6 +434,7 @@ To configure the use of an Amazon AWS ALB ingress controller in the addons.yaml
 - Specify your EKS cluster name in the `clusterName: <YOUR_EKS_CLUSTER_NAME>` parameter.
 - Specify the region of your EKS cluster name in the `region: <YOUR_EKS_CLUSTER_REGION>` parameter. Resources created by the ALB Ingress controller will be prefixed with this string.
 - Specify the the AWS VPC ID of your EKS cluster name in the `VpcID: <YOUR_EKS_CLUSTER_VPC_ID>` parameter. You must enter your VPC ID here if ec2metadata is unavailable from the controller pod.
+- Uncomment and specify the Amazon EKS Amazon ECR image repository in the image.repository: <Amazon EKS Amazon ECR image repository> parameter. This is required for AWS GovCloud deployments
 - Specify complete  required required annotation to specify the role that you associate with the primary IAM user who is responsible for your EKS deployment in the `serviceAccount.annotations.eks.amazonaws.com/role-arn: <YOUR_IAM_ROLE_ARN>` parameter.
 
 To ensure logging for your deployment is properly configured to take advantage of the built-in EFK logging tools in EKS deployments, refer to the [Amazon EKS Workshop](https://eksworkshop.com/logging/).