10 ms·
GCP to introduce an additional charge for publicly addressed VM instances
- QUFB 7y agoAnd yet IPv6 connectivity is still not available for GCE instance VMs.
- privateSFacct 7y agoIPv6 is not yet that useful for external facing sites (what do people use IPv6 for on external sites?), but AWS does let you get a /56 for a VPC which should be enough for most VPC need (you can't specify your own CIDR however).
- profmonocle 7y ago> IPv6 is not yet that useful for external facing sites Google's NAT pricing only affects connections initiated by the VM (external load balancer traffic doesn't use the NAT). So most of this traffic is going to be your servers talking to 3rd party APIs, update servers, etc. A lot of these services support IPv6 now, meaning your NAT costs would be lower if GCE supported IPv6.
- sieabahlpark 7y agoBut then they couldn't charge you for the bandwidth.
- manigandham 7y agoWhy not? IPv6 usage is increasing every year and offers faster, simpler routing which results in better performance. Almost all mobile networks (which is about half the traffic today) use IPv6.
- blibble 7y agoI'll be moving my VMs to AWS, given this almost doubles the costs of the smallest instances
- deleted 7y ago[deleted]
- privateSFacct 7y agoEIP's are 0.01/hr I think on AWS. But if you can deal with an amazon ephemeral IP you can usually get those for free.
- miyuru 7y agoThats only when the EIP is not attached to a running instance. If its associated with a running instance there is no charge.
- morpheuskafka 7y agoEIPs are free and there is no plan to change that as far as we know today. You're thinking of the unused EIP penalty fee, which GCP and everyone else has long had an equivalent to.
- srj 7y agoHave you looked into using Cloud NAT? Do you need all those ephemeral v4 IPs? (I work in Google Cloud Networking -- though not this particular area.)
- profmonocle 7y agoI've said this elsewhere in the thread, but Cloud NAT is kind of expensive. 4.5¢ per GB increases egress costs by 37.5% (normally 12¢ per GB) plus it applies to ingress as well, which is usually free. Sure it doesn't apply to inbound traffic through load balancers, but if you transfer a lot of data to/from external APIs (i.e. connections by the instance) that could seriously add up. Based on my company's usage, it will almost certainly be cheaper for us to just pay the $2.92/instance/month to keep using public V4 addresses on our GKE nodes.
- cameronbrown 7y agoThis seriously hurts some of my use cases: 1. Running a website on GCE 24/7 2. Running a Minecraft/CS:GO server for 10hr/day There's no situation where I won't be paying more. Plus these games don't really support IPv6.
- reilly3000 7y agoThis is cheaper than AWS EIP for instances that are using an EIP. It is free for GCP VMs to have a resevered IP and use it vs $3.60/mo for AWS EIP whether its used or not. With GCP, unused reserved IP is $7.20/mo. I can't think of a lot of scenarios where you need to hold on to an IP you're not using for an extended period of time, but I could be wrong.
- openstep 7y agohuh? aws eip is free if you're using it on an ec2 instance
- mitchs 7y agoAmazon EIPs are free when attached to a running VM. (Unless you have more than one attached to the same VM.)
- vasco 7y agoEIPs are free when attached. And public addressable instances in AWS do not need an attached EIP, that's only if you want the public IP to be static and to be able to replace the instance without updating DNS records. So both are free compared to GCP's paid.
- miyuru 7y agoAl least provide proper IPv6 support before charging for IP addresses.
- privateSFacct 7y agoGCP has marketed their amazing network so its interesting this isn't supported.
- profmonocle 7y agoWhat's weird to me is that Google itself has excellent IPv6 support. Every Google web site, API, or other service I've come across fully supports IPv6. Compute Engine VMs are the outlier. They actually utilize this for their "private Google access" system, which allows you to access Google services from a compute engine VM without a public v4 address. The VM's private v4 address gets mapped into an IPv6 address, along with some extra bytes identifying the customer's network. (You can see this by setting up such a VM and accessing an AppSpot app that echos your source IP.)
- outside1234 7y agoGCP is like this ghetto inside of Google. Worse talent, worse network, ...
- zettatron 7y agoHilarious. How poor is the talent on the GCP team that is foremost of your grievances?
- big_chungus 7y agoUhh, that's sort of a relevant "grievance" in a thread on GCP issues.
- sieabahlpark 7y agoUnlike AWS which needs to be good to not go out of business.
- profmonocle 7y agoCloud NAT would be fine except it costs 4.5¢ per GB (in both directions) which could hurt some use cases. If your backend VMs pull in more than 64.8 GB per month from the Internet it's cheaper to just pay for the public IP. (Only applies to outbound connections initiated by the VM, inbound connections through load balancers don't go through the NAT.) I'll echo what others have said - it sucks that they're doing this before adding IPv6 support. A good portion of traffic could bypass the NAT entirely considering how many services support IPv6 these days. They don't start charging until April, so maybe they'll surprise us with an IPv6 announcement before then, but I'm not betting on it. :(
- sandGorgon 7y agoThe cloud NAT is not for avoiding ip costs. Lot of external services need whitelisted IP. And in the world of k8s and on-demand instances, NAT is pretty much the only way one can guarantee static outbound IP.
- profmonocle 7y ago> The cloud NAT is not for avoiding ip costs. Well, it wasn't before now, since it's always been more expensive. But they're trying to sell it that way. OP's link doesn't mention it, but the email I got also announced a Cloud NAT price drop. There's currently a $32.85 flat fee per region to use Cloud NAT (on top of the per-GB fee). They're lowering this to $1.022 per VM per month, capped at $32.12 total. (They're also capping the per-GB fee to 4.5 cents per GB worldwide, it's currently higher in some regions.) Of course, the flat fee is peanuts for any substantial cloud project, but the fact that they announced them side-by-side means they consider Cloud NAT a way to save on this new IP charge.
- deleted 7y ago[deleted]
- vast 7y agoSlightly off topic: how does cloud NAT scale. The defaults are way too low for request heavy projects and the regarding docs were kinda hard to understand for a non ops guy.
- jmb12686 7y agoThis definitely limits the usefulness of Google's "always free" tier. This will x2 some bills I have for small personal projects, though will still be a bit cheaper than an AWS alternative after the 12 month free tier. Sigh.. I suppose it was a matter of time before they figured out the pricing loophole. Back to creating new Google accounts every year to get the year of credits...
- jayd16 7y agoShhhhhhhhut uuuuup
- cameronbrown 7y ago> Back to creating new Google accounts every year to get the year of credits... I'd be careful doing this. You wouldn't want their automated systems to ban all your accounts + personal one by association.
- JamesBrooks 7y agoI don't know - seems like a really good opportunity to finally kick that Google habit like I've been meaning to do ;)
- 7y ago
- mjcarden 7y agoDarn. The tiny VM I have hosting my Quassel server for always-on IRC will go from approx 20 Australian cents per month to approx $4.30 per month. That's a rather large jump.
- xkgt 7y agoThis is silly and will further harm GCP's viability as alternative to AWS or Azure. Firstly, I can't find any official announcement regarding the rationale and suggested solutions for their customers to reduce their cost. Just adding a banner to docs pages is plain lazy and is not customer friendly. Ideally IPv6 support should have been added or at least scheduled to be available at instance level [1] before enforcing such charges. This indicates a lack of engineering capability (more likely resource commitment) to implement such a critical feature on its platform in a timely manner, particularly given that its rivals already have the support in place. To me, that is more worrying than an increase in bill. What is the pace of innovation one can expect from GCP platform? How committed are its leaders as a public cloud service provider? 1. https://googlecloudplatform.uservoice.com/forums/302595-compute-engine/suggestions/8518246-support-ipv6 https://googlecloudplatform.uservoice.com/forums/302595-comp...
- AaronFriel 7y agoNot to detract from what you're saying about IPv6: support there is key. Azure and AWS both support IPv6. That said, Azure charges for IPv4 external IPs. AWS does not, but I'd be surprised if the cost wasn't internally associated with ELB/ALB, EC2 instances, or other products. That is, you're still paying for it.
- omeid2 7y agoSure, you're paying for everything you use, but the difference is when you compare costs. The less "addons" you need, the more true is the cost.
- ben509 7y agoWhile elastic IPs are free for an active instance, AWS does charge for unused EIPs[1]. (You can also set a public IP on an instance, but it can change when the instance is restarted.) So if you need to hold on to an IPv4 address, it's going to cost you. That seems like it's exactly the same model as GCP. [1]: https://aws.amazon.com/premiumsupport/knowledge-center/elastic-ip-charges/ https://aws.amazon.com/premiumsupport/knowledge-center/elast...
- baggy_trough 7y agoThe network continues to be an annoyingly expensive part of GCP.
- londons_explore 7y agoAnnoyingly expensive part of all cloud providers... I think thats deliberate - for most businesses, the cost of networking is directly proportional to how many customers you have, whereas the cost of compute isn't so tightly coupled. Startups really care about costs to get started, and aren't so worried about costs when they have a billion customers.
- baggy_trough 7y agoNot all of them. Linode has very cheap network, for example.
- ggm 7y agoIf you were in the always free tier, you weren't revenue neutral, you cost google money. This just amplifies the truth a bit: being 24/7 on somebody else's hardware incurs costs, even if you are surprised when the bill of fare is presented (disclaimer: I work in the internet number ecosystem so I am not un-involved)
- clhodapp 7y agoAh well except it is literally called the "always free" tier so you would think that something as core as being connected to the internet would be, you know... free?
- ggm 7y agoDid they promise you'd have a static IP? 99% or more of the internet for free is behind CGN or home NAT and has little or no persisting address binding for incoming, hence ddns services. Did google distinguish as saying in the 'forever free' bucket they'd do that? being "on" the net is not the same as being "always reachable at a stable IP endpoint"
- MGATOR 7y agoCorrect me if I'm wrong, but it sounds like they are going to charge for ephemeral IP addresses as well, not just static ones. This means any VM which accesses an external service via IPV4, i.e. making a request to a transactional mail service, will now have to pay for this privilege even if ingress is via a load balancer.
- ggm 7y agoI understood it to be a fee for static IP binding, used or reserved. Sad to be corrected (I mean, happy to be corrected but the news won't be happy)
- clhodapp 7y agoYou are incorrect. They are going to begin charging a small fee for public IPs (i.e. IPs that can talk to the internet), not static IPs. They do support NAT as an alternative, but they charge for it (and are slightly lowering that cost as a part of this change). To be clear, none of this is going to have any measurable impact on me, I'm just pointing out the fact that they didn't really hold true to the promise of the free tier. Source: the email that they sent out to customers about this
- penagwin 7y agoI don't understand this move, over 2$ month extra for any ipv4 address? Are we actually running out of addresses or is this a money grab kinda thing? Most of the competitors I know of offer one free ipv4, often a block of ipv6, and extra ipv4 addresses are normally only a dollar or two at most a month extra Like many others said, this can double the cost of small projects.
- profmonocle 7y ago> Are we actually running out of addresses or is this a money grab kinda thing? We "ran out" some time ago. Of course, IP addresses don't get used up, so this can be defined different ways. It's no longer possible to get brand new (i.e. never used) IP addresses from the regional registries, so the only way to get a block is to buy it from another company. Cloud companies have been buying up IPv4 space like crazy since the registries ran out. A couple years ago Amazon bought half of MIT's /8 block, and just a few weeks ago they bought a quarter of the /8 that was originally set aside for HAM radio. So we'll never exactly "run out" per se. It's like real estate. They're not making more, but you can still buy it. It just gets more expensive. (And hopefully we eventually move to IPv6 which isn't so maddeningly restricted.)
- londons_explore 7y agoAnd Google hasn't been buying up big blocks like that, so are probably running out, so are having to introduce a charge for them...
- Havoc 7y ago>And Google hasn't been buying up big blocks like that, so are probably running out That seems like poor planning for a big cloud provider if true. IPV4 will unfortunately be around for a while
- pdkl95 7y ago> Are we actually running out of addresses We ran out a long time ago: IANA Unallocated Address Pool Exhaustion: 03-Feb-2011 Projected RIR Address Pool Exhaustion Dates: RIR Projected Exhaustion Date Remaining Addr in RIR Pool (/8s) APNIC: 19-Apr-2011 (actual) 0.1946 RIPE NCC: 14-Sep-2012 (actual) 0.1289 LACNIC: 10-Jun-2014 (actual) 0.0351 ARIN: 24 Sep-2015 (actual) 0.0002 AFRINIC: 08-Feb-2020 0.2940 http://www.potaroo.net/tools/ipv4/index.html http://www.potaroo.net/tools/ipv4/index.html
- deepsun 7y agoToo bad K8S doesn't support IPv6 at all.
- Rockjodd 7y agosig-network is working hard to get dual stack support in. https://github.com/kubernetes/enhancements/issues/563 https://github.com/kubernetes/enhancements/issues/563 It was supposed to be targeting 1.16, but looks like it will be in 1.17 according to https://github.com/kubernetes/enhancements/issues/508#issuecomment-516862747 https://github.com/kubernetes/enhancements/issues/508#issuec...
- linuxdude314 7y agoThat is completely untrue. Kubernetes has full support for IPv6. https://github.com/kubernetes/enhancements/issues/508 https://github.com/kubernetes/enhancements/issues/508
- Rockjodd 7y agoWe still want it to be promoted to beta, so it is actually available in GKE and other cloud vendors. Alpha level cluster in GKE gets wiped every 30 days, nothing you want to run any production workload on. Of course you have the option of self-hosting..
- jasonvorhe 7y agoIf you can't move your workloads to a new cluster within 30 days, you should reflect on how you're using Kubernetes.
- Sami_Lehtinen 7y agoThis is definition question. As example Scaleway offers free public IPv4 address, but if you don't want it, then you'll get discount. - Are they charging for it?
- kccqzy 7y agoI find this doc confusing. In the blue box it appears that all external IPv4 addresses will be charged, but in the paragraph immediately below, it says: > If you reserve a static external IP address but do not use it, you will be charged […]. If you reserve a static external IP address and use it […] you will not be charged for it. This seems like two very different kinds of charges. So is Google changing its policy with just one blue box? Or is the documentation in error? I suppose it's the former but it's not clear.
- 9nGQluzmnq3M 7y agoCurrently you're charged only for unused external IPv4 addresses. Starting January 1st, 2020, you'll receive a bill showing how much you would pay under the new scheme that charges for all external IPs, but won't actually pay yet. Actual billing starts April 1st, 2020.
- londons_explore 7y agoThats a while 9 months for them to give a free allowance of IP's (say 5 per account), support IPv6, or backtrack on the plans entirely.
- iamjustlooking 7y agoIt feels like GCP figured out a way to charge for ingress. I can get behind using NAT instead of our instances having external IP's but a 4.5¢/GB hit on egress AND ingress traffic is hard to swallow.
- kerng 7y agoAt times I think Google should move some of their core teams over to GCP. It seems like they dont know what they are doing. The hiring bar also appears much lower at GCP. Makes you wonder how important Google sees GCP, or they think the train has already left...
- treggle 7y agoThere’s a growing number of reasons to consider exiting the major clouds.
- SanchoPanda 7y agoAs cloud becomes the default for small to mid scale computing, storage and networking, the patience for hiccups due to roll your own solutions falls as well.
- nullify88 7y agoPreviously, Windows instances required a public IP address in order to connect to and retrieve a license from Googles KMS server. Looks like that has changed recently, and this news had me worried we'd have to pay extra for our Windows instances. So at least now I can save a few pennies and IP addresses. https://cloud.google.com/compute/docs/instances/windows/creating-managing-windows-instances#kms-server https://cloud.google.com/compute/docs/instances/windows/crea...
- acd 7y agoHow about also offering ipv6 public ip for free? Then we would get higher adoption rate for ipv6
- londons_explore 7y agoNotice very few Google employees commenting in this thread? My guess is they have further announcements planned, and perhaps this documentation change was inadvertantly pushed out early... I'd be hoping to see one or more of: * 1 free IP per account * free shared HTTP loadbalancing * IPv6 support
- shusson 7y ago> 1 free IP per account I hope so
- shusson 7y agoI really hope they add one free static external ip in the always free tier.
- xxxpupugo 7y agoNot a big deal, the bucks are tiny.
- Havoc 7y ago>$0.004 per hour >8760 hours in year so 35 USD So much for free tier to host low traffic websites. Good bye and thanks for all the fish! The free VM & ip was appreciated while it lasted :) Fortunately I built everything on a Ubuntu VM...so damn near any provider works for me.
- sitkack 7y agoI recommend DO for stuff like this, they are also great a cross cloud mechanism for health checks and dashboards. Never put all your eggs in one basket.
- yjftsjthsd-h 7y agoIf you were previously entirely on the free tier, what provider are you moving to that's cost-competitive even against $35 a year?
- Havoc 7y agoI've still got a LowEndTalk forums special kicking around somewhere. 15 Eur per year for a 2 CPU/1GB/ipv4/1TB traffic KVM. edit...its one from alpha vps. So far so good - feel snappier than a google free vm. But that was on a deep discount special. It's not that hard to find cheap stuff on specials if you're ok with taking a calculated risk on the providers. If I go the cloud route I'll probably jump on a Azure of AWS intro credit plan.
- tgtweak 7y agoOn another note: $7/mo for an unused static IP...??? The public instance fee feels like the plastic bag fee at the grocery store - ipv4 space is indeed finite. It is reasonable to assume it costs more to run a VM with public access than without, but to charge for it?
- exabrial 7y agoConveniently, SRV records were eschewed from http3 which would greatly diminish the need for this.
- maciel310 7y agoLooks like the Always Free page was updated to include a free IP too, so you'll still be able to use it for free cloud hosting of small loads. "Each month, eligible use of all of your f1-micro instances and associated external IP addresses are free until you have used a number of hours equal to the total hours in the current month" - https://cloud.google.com/free/docs/gcp-free-tier https://cloud.google.com/free/docs/gcp-free-tier Wasn't there last time archive.org crawled the page, so it is a new addition.