Good way to whitelist ingress traffic for JHub on EKS (AWS kubernetes)?

I have a EKS cluster (EKS is AWS’ managed kubernetes service).
I deploy an application to this EKS cluster (JupyterHub) via helm.
I have a VPN server.
Users of my application (JupyterHub on EKS) must connect to the VPN server first before they access the application.
I enforce this by removing the “allow all” ingress rule on the elastic load balancer, and adding an ingress rule that allows traffic from the VPN server only.
The elastic load balancer referenced above is created implicitly by the JupyterHub application that gets deployed to EKS via helm.

When I deploy changes to the running JuypyterHub application in EKS, sometimes [depending on the changes] the ELB gets deleted and re-created.
This causes the security group associated with the ELB to also get re-created, along with the ingress rules.
This is not ideal because it is easy to overlook this when deploying changes to JupyterHub/EKS, and a developer might forget to verify the security group rules are still present.

Is there a more robust place I can enforce this ingress network rule (only allow traffic from VPN server) ?

Two thoughts I had, but are not ideal:

  • Use a NACL. This won’t work really, because it adds a lot of overhead managing the CIDRs due to the fact NACL is stateful and operates at subnet level.
  • I thought to add my ingress rules to the security group associated with the EKS worker nodes instead, but this won’t work due to the same problem. When you delpoy an update to Jupyterhub/EKS, and if the ELB gets replaced, a “allow all traffic” ingress rule is implicitly added to the EKS worker node security group (allowing all traffic from the ELB). This would override my ingress rule.