Update ALB Controller to provision NLBs #69
Conversation
reconfigure Ingress to give the ALB 'LoadBalancer' servive type for NLB configuration
…nx service
* NLB is provisioned
* Target groups appear healthy
* DNS entry is created
* Traffic is getting all the way through to the ingress-nginx controller ("400 bad request" from nginx)
Parsing the LB name out of 'data.kubernetes_service.ingress_service' is hard, so let's see if this passes
Also removes some extraneous parameters (the defaults are fine), and configures the controller to pass through the real client IP.
It's 'degraded' until it has enough replicas in EKS which varies on the number of nodes in the EKS cluster, it then becomes 'active'
|
Before we merge this, I want to verify that we have no issues uploading a solr configset. We might need the 307 Redirect implemented somewhere. Will update soon! 😀 |
|
Success!! 🥳 |
That makes a lot more sense as to why you wanted to document it. I think this becomes a very niche use case of using both the |
Related to GSA/data.gov#3677
New Additions:
Upgrades:
AWS LB Controllerto 2.3