Nit: Naming consistency

[bryantbiggs]

The various names used across the project are not consistent and can be rather confusing. Could we standardize the naming conventions a bit - happy to help update once a convention has been established

Current references

• Repository name: aws-application-networking-k8s
• Docs site name: AWS Gateway API Controller
• Chart name: aws-gateway-controller-chart
• Namespace name: aws-application-networking-system
• Service account name: gateway-api-controller
• Policy name (from getting started): VPCLatticeControllerIAMPolicy

An example proposal

• Repository name: aws-gateway-api
• Docs site name: AWS Gateway API
• Chart name: aws-gateway-api
• Namespace name: aws-gateway-api
• Service account name: aws-gateway-api
• Policy name (from getting started): AwsGatewayApiController

Why aws-gateway-api?

1. The upstream convention is K8s/Kubernetes Gateway API
2. Avoids confusion with Amazon API Gateway by having the API after the Gateway

[bryantbiggs]

After some thought, I think the names proposed above are too generic; something like the following might be more appropriate:

• Repository name: aws-vpc-lattice-controller
• Docs site name: AWS VPC Lattice Controller
• Chart name: aws-vpc-lattice-controller
• Namespace name: aws-vpc-lattice-controller
• Service account name: aws-vpc-lattice-controller
• Policy name (from getting started): AwsVpcLatticeController

Or if this project is meant to hold implementations for both VPC Lattice and ALB/NLB:

• Repository name: aws-gateway-api
• Docs site name: AWS Gateway API
• VPC Lattice
  • Chart name: aws-vpc-lattice-controller
  • Namespace name: aws-vpc-lattice-controller
  • Service account name: aws-vpc-lattice-controller
  • Policy name (from getting started): AwsVpcLatticeController
• ALB/NLB
  • Chart name: aws-load-blancer-controller
  • Namespace name: aws-load-blancer-controller
  • Service account name: aws-load-blancer-controller
  • Policy name (from getting started): AwsLoadBlancerController

[bryantbiggs]

Latest proposal:

• Repository name: aws-application-networking-k8s -> aws-gateway-controller
• Docs site name: AWS Gateway API Controller -> AWS Gateway Controller
• Chart name: aws-gateway-controller-chart -> aws-gateway-controller (note: git tag can have -chart, but name of the chart should not have -chart)
• Namespace name: aws-application-networking-system -> aws-gateway-controller
• Service account name: gateway-api-controller -> vpc-lattice (will have others for alb, appmesh, etc. to map to IRSA/secret)
• Policy name (from getting started): VPCLatticeControllerIAMPolicy -> AWSGatewayController-VPCLattice

[zmingxi]

Thank you for your suggestion! We really appreciate it. We will look into it and get back to you as soon as we can.