Simplify IpPoolSelector and call sites

[david-crespo]

IpPoolSelector is used on instance create, floating IP create, and ephemeral IP attach, but most of the logic inside only applied to instance create. Here I:

• Move logic that syncs the selected pool with the selected IP stack on the network interface of out IpPoolSelector and into instance create (the only call site that cares)
  • The IpPoolSelector props are simpler — removed ipVersionFieldName, currentPool, and setValue
• Move default pool logic out of useEffects and into useForm defaultValues
  • In order to do this, floating IP create now prefetches pools via loader instead of fetching lazily with useQuery
• Floating IP create no longer hides the pool selector behind the "Advanced" accordion — it's now always visible
• Derive ipVersion at submit time instead of keeping track of it in the form state

I don't think any actual behavior should change here.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
console	Ready	Preview	Feb 4, 2026 9:56pm

[david-crespo]

this is not necessary at all if you derive it at submit time

[david-crespo]

I think this is only really necessary for instance create because that's the only one where the stack can change. We calculate it for ephemeral IP modal but we can do it once up front because it's in the context of an instance where the stack is fixed.

[david-crespo]

Note v4 fallback where when there are no defaults doesn't really make sense because auto will fail in that case. What we should do is make the user pick. The simplest thing would be to always make the user pick and just not use the auto side here.

[charliepark]

I believe this is now how you have it, where the form is disabled with the No default compatible pool available; select a pool to continue message, so I don't know that anyone is going to end up hitting this.

[david-crespo]

Ah, that's right. Insight applied here for more cleanup 72b671a

[charliepark]

So clean