René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Switch nginx ingress to use NLB","articleBody":"The current setup uses ELB for the nginx ingress controller, but there would be some benefits to switching over to NLB:\n- With the current setup we don't get remote IPs in nginx logs\n- We are already using L4 only on the ELB so why not, when NLB is better and more efficient at handling it.\n\n\nThe change should be straightforward, it will just require some testing.\n\nThese annotations need to be added to the ingress service:\n```\n    service.beta.kubernetes.io/aws-load-balancer-type: nlb\n    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp\n    service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: '60'\n    service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: 'true'\n```\n\nThe nginx default keepalive timeout is 75s but let's also specify that explicitly in the code, maybe with a comment telling people that the lb timeout must be shorter than the nginx keepalive.\n\nAfter this change, make sure that the nginx logs show the proper remote IP address, not an internal `10.` address.\nMake sure TLS still works properly. \n","author":{"url":"https://github.com/bmonkman","@type":"Person","name":"bmonkman"},"datePublished":"2021-03-03T02:00:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/184/zero-aws-eks-stack/issues/184"}