To allow customers to save cost and eliminate complexity, each blueprint cluster will only leverage a single load balance. The load balancer will direct traffic to Nginx running in the cluster which will serve as a reverse proxy and forward requests to the appropriate service. The load balancer will be responsible for terminating TLS as well which will give all services running in the cluster TLS out of the box. A big win for customers. We need to enable this functionality via the Nginx addon.
@shapirov103 this one is likely going to fall in your court. We are going to need to think through how customers will be able to supply a custom domain to us. For instance, if I own a cluster in us-west-1, it is a "dev" cluster, and is running a workload called payments, I might want a url that looks like https://payments.dev.us-west-1.coleman.com How do we offer this functionality out the of box?
As part of this ticket, we will also need to:
[ ] document how all of this works
[ ] Add sample ingress objects to actual sample workloads.
To allow customers to save cost and eliminate complexity, each blueprint cluster will only leverage a single load balance. The load balancer will direct traffic to Nginx running in the cluster which will serve as a reverse proxy and forward requests to the appropriate service. The load balancer will be responsible for terminating TLS as well which will give all services running in the cluster TLS out of the box. A big win for customers. We need to enable this functionality via the Nginx addon.
@shapirov103 this one is likely going to fall in your court. We are going to need to think through how customers will be able to supply a custom domain to us. For instance, if I own a cluster in us-west-1, it is a "dev" cluster, and is running a workload called
payments, I might want a url that looks likehttps://payments.dev.us-west-1.coleman.comHow do we offer this functionality out the of box?As part of this ticket, we will also need to: [ ] document how all of this works [ ] Add sample ingress objects to actual sample workloads.
Other references
https://aws.amazon.com/premiumsupport/knowledge-center/terminate-https-traffic-eks-acm/