Public setup IP Unreliable
Hey, just relaying some feedback (or requesting some guidance if I'm mistaken).
Details:
- I'm using runpod through the GraphQL API primarily.
- When creating a pod using
podFindAndDeployOnDemand, I set ports: "22/tcp", supportPublicIp: true and startSsh: true.
- Occasionally however, I receive a pod which has no public address/only supports the proxied basic SSH access.
Would be great if podFindAndDeployOnDemand request would simply fail if no pod can be created with a public IP, rather than returning a normal pod.9 Replies
Im a bit unfamiliar with this IP stuff but is this community cloud or secure cloud? I think reading previous stuff community cloud doesn’t guarantee public Ips while secure cloud does
Expose ports | RunPod Documentation
Learn to expose your ports.
Yes, some pods don't have a public IP, but if you sepecifically select that you want a public IP in your GraphQL API call, you must get a pod that DOES have a public IP. If you specify that you want a public IP and don't get one, then this is a bug.
Ah yes then I think there's a bug here. Getting this on both secure and community cloud intermittently
@Justin Merrell *just flagging to runpod staff, that graphql might not be guaranteeing public ips correctly
As anyone else replicated this? I can try in a bit
I had it a few times when I used to use GraphQL but now I use the Web console and it hasn't happened once.
I just tested 4 different pods that I created using GraphQL and every single one of them got public IP successfully.
Just happened to me 10 minutes ago with some A100's in US secure cloud, happens ~15% of the time so not sure how easy it would be to replicate reliably