Ingress Fails to Assign IP When Deploying Pomerium as NodePort

[hamzabouissi]

What happened?

Recently we wanted to deploy pomerium svc as nodeport using argocd and we noticed the app stuck at progressing state, we found out inrgess address aren't getting any ip and that made the argocd health check on ingress resources fails

What did you expect to happen?

we expected the ingress controller to assign an IP to ingress address when using pomerium svc as NodePort

How'd it happen?

just change pomerium svc type from LoadBalancer to NodePort

What's your environment like?

• pomerium version: v0.27.2
• kubernetes 1.30.0 or newer

What's your config.yaml?

N/A

What did you see in the logs?

no useful outputs

Additional context

[hamzabouissi]

here is my pr: #1099

[venkatamutyala]

Hey @desimone, is there anyone on your team that might be able to look at this PR? We (@hamzabouissi) tested it on our end and it appears to be working as expected. We would love to work with you folks to get this merged back into your repository instead of having to maintain a fork on our end.

Regards,
Venkat @ GlueOps