-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Comments
+1 Received same mail. Should be specified in the documentation |
I updated my instance today from F1-micro to E2-micro with no issues by following change machine type GCP docs. Pi-Hole admin dashboard and output from these two test sites look good after reactivating WireGuard: |
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. |
I can agree, you can't create any f1-micro anymore. The free tier is now e2-micro-VM 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. |
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:
The text was updated successfully, but these errors were encountered: