Open bryantbiggs opened 1 year ago
After some thought, I think the names proposed above are too generic; something like the following might be more appropriate:
aws-vpc-lattice-controller
AWS VPC Lattice Controller
aws-vpc-lattice-controller
aws-vpc-lattice-controller
aws-vpc-lattice-controller
AwsVpcLatticeController
Or if this project is meant to hold implementations for both VPC Lattice and ALB/NLB:
aws-gateway-api
AWS Gateway API
aws-vpc-lattice-controller
aws-vpc-lattice-controller
aws-vpc-lattice-controller
AwsVpcLatticeController
aws-load-blancer-controller
aws-load-blancer-controller
aws-load-blancer-controller
AwsLoadBlancerController
Latest proposal:
aws-application-networking-k8s
-> aws-gateway-controller
AWS Gateway API Controller
-> AWS Gateway Controller
aws-gateway-controller-chart
-> aws-gateway-controller
(note: git tag can have -chart
, but name of the chart should not have -chart
)aws-application-networking-system
-> aws-gateway-controller
gateway-api-controller
-> vpc-lattice
(will have others for alb
, appmesh
, etc. to map to IRSA/secret)VPCLatticeControllerIAMPolicy
-> AWSGatewayController-VPCLattice
Thank you for your suggestion! We really appreciate it. We will look into it and get back to you as soon as we can.
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
aws-application-networking-k8s
AWS Gateway API Controller
aws-gateway-controller-chart
aws-application-networking-system
gateway-api-controller
VPCLatticeControllerIAMPolicy
An example proposal
aws-gateway-api
AWS Gateway API
aws-gateway-api
aws-gateway-api
aws-gateway-api
AwsGatewayApiController
Why
aws-gateway-api
?K8s/Kubernetes Gateway API
API
after theGateway