Scaleway STARDUST1-S Instance Type Support

[emolitor]

Scaleway now has a STARDUST1-S Instance Type "STARDUST1-S"
1 vCPU, 1 GB of RAM, 1 IPv4 address, 10GB storage, up-to 100Mbps Bandwidth. €0.0025/hour.

Having support for this would be by far the lowest cost option to use with inlets for European customers. It would be nice to add support for Amsterdam regions as well.

[alexellis]

Thank you for the suggestion. We will take a look.

Pinging @jsiebens

Also, check out Fly.io where you can run three tunnels for free: https://inlets.dev/blog/2021/07/07/inlets-fly-tutorial.html

[dirien]

I love the stardust instances. The ony thing could be the reliability on the availability:

Every month, limited numbers of Stardust Instances will be released

Stardust stocks will be limited at launch: one Stardust in PAR1, one in AMS1…if you are quick enough to get one!
More instances will be added to the pool regularly. These exclusive releases are called Stardust rain, and you don’t want to miss them. Here’s how it works.

I am not sure how to work with this Stardust rain events in inlets. One idea could be a cascading provisioning. First try to provision a stardust in the prefered region. Iterate to the next region or fallback to the developer instance.

Or adding a stardust flag (--promo-instance 😄 )...

[alexellis]

It sounds like if you can get one of these instances then you are very lucky to have it and are allowed only one.

For that reason it may not make a good fit in our automation tools.

But don't let that stop you installing inlets PRO onto any VM you been provision.

Let us know if Scaleway changes their policy and we can reconsider.

[jsiebens]

This library already supports using a certain plan and/or region, so no changes are required here.

Both tools using this library (inletsctl and inlets-operator) have already a flag to select a region, perhaps we could add a flag to select the plan as well.

[alexellis]

The flag is available but only set if on Equinix Metal. Happy for someone to update inletsctl to accept the plan flag for the other provisioners. Should be an easy PR for someone to make

[emolitor]

Depending on how busy my weekend is I might take a stab at this. - Eric

…

On Mon, Jul 19, 2021 at 12:50 PM Alex Ellis ***@***.***> wrote: The flag is available but only set if on Equinix Metal. Happy for someone to update inletsctl to accept the plan flag for the other provisioners. Should be an easy PR for someone to make — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAECQN7NTVCKPRXKGVWN4H3TYQGPJANCNFSM5ASEC2ZQ> .

[jsiebens]

I had a little bit of time this evening: inlets/inletsctl#106

[dirien]

noice! ❤️

[alexellis]

Looks like we may have got there sooner than expected @emolitor, but it'd be great if you can test it on your setup.

I've cut a new release binary

[emolitor]

Thanks, will be able to test tomorrow.

…

On Wed, Jul 21, 2021 at 9:13 PM Alex Ellis ***@***.***> wrote: Looks like we may have got there sooner than expected @emolitor <https://github.com/emolitor>, but it'd be great if you can test it on your setup. I've cut a new release binary — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAECQNY47BALP7LEAF2FYXTTY4TALANCNFSM5ASEC2ZQ> .

[emolitor]

Works for me, many thanks everyone!

[dirien]

For everyone stumbling over this: Keep in mind to check, in which region a stardust instance is available and set --region too!

inletsctl create --provider scaleway ... --plan=STARDUST1-S --region=ams1|par1