What steps did you take and what happened:
I have ApiLbLocation configured for my WAN IP (not 0.0.0.0\0 )
During cluster build of master node, the ApiLoadBalancerSecGroup blocked TCP traffic back thru the NAT Gateway via its public ip (NATEIP).
What did you expect to happen:
Successful cluster buildout.
Anything else you would like to add:
You could document that its easiest to just set ApiLbLocation = 0.0.0.0 at first.
Let everything build out, and then manually change ApiLoadBalancerSecGroup to something more restrictive.
What steps did you take and what happened: I have ApiLbLocation configured for my WAN IP (not 0.0.0.0\0 ) During cluster build of master node, the ApiLoadBalancerSecGroup blocked TCP traffic back thru the NAT Gateway via its public ip (NATEIP).
What did you expect to happen: Successful cluster buildout.
Anything else you would like to add: You could document that its easiest to just set ApiLbLocation = 0.0.0.0 at first.
Let everything build out, and then manually change ApiLoadBalancerSecGroup to something more restrictive.
Environment:
kubectl version
):/etc/os-release
):