Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade F1-micro to E2-Micro by Aug. 31, 2021 #45

Open
nickFalcone opened this issue Jul 20, 2021 · 4 comments
Open

Upgrade F1-micro to E2-Micro by Aug. 31, 2021 #45

nickFalcone opened this issue Jul 20, 2021 · 4 comments

Comments

@nickFalcone
Copy link

I received an email from GCP instructing me to change my F1-micro instance to E2-micro by August 31, 2021 to continue using the free tier. The E2-micro free tier becomes available on August 1, 2021.

I will attempt to change over on August 1st. I opened this issue to track documentation updates in GOOGLE-CLOUD.md where there are references to the F1-micro VM.

Email excerpt below:

What do I need to know?
The Free Tier F1-micro VM is changing to the E2-micro VM as the VM to use for free. On August 1, 2021, E2-micro Free Tier will be introduced. Follow these steps to change your machine type to E2-micro to avoid incurring charges for continuing to use F1-micro after August 31, 2021.

What do I need to do?
Starting August 1, 2021, change the machine type from F1-micro, or stop your existing F1-micro instance and begin using a E2-micro instance. VMs created with either method will automatically have the Free Tier discount applied to them. The supported regions will remain the same.

@Kwbmm
Copy link
Contributor

Kwbmm commented Jul 25, 2021

+1 Received same mail. Should be specified in the documentation

@nickFalcone
Copy link
Author

I updated my instance today from F1-micro to E2-micro with no issues by following change machine type GCP docs.

e2Micro

Pi-Hole admin dashboard and output from these two test sites look good after reactivating WireGuard:

@jcat59
Copy link

jcat59 commented Sep 10, 2021

FYI - I followed the guide and my only change was to use the E2 instance based on this comment. Everything worked great.

As a side note, I accidentally chose the 'balanced persistent disk' rather than the 'standard persistent disk', and realized after I started getting charges. Had to figure out how to stop the VM, make a snapshot of the disk, move the VM to the new disk, then delete the old disk. Everything back up and running now. --- in the process, learned it's not a bad idea to save a snapshot every once in awhile anyways.

@dd8zc
Copy link

dd8zc commented Mar 8, 2022

I can agree, you can't create any f1-micro anymore. The free tier is now e2-micro-VM
https://cloud.google.com/free/docs/gcp-free-tier/#compute

To be precise "1 vCPU + 614MB RAM f1-micro virtual machine instance per month in one of the following US regions:" isn't correct anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants