[Improvement]: Add instructions for increasing resources for GitHub Enterprise Server instances on Google Cloud Platform

[docs-bot]

What feature or product is affected?

GitHub Enterprise Server.

What is the new or expected behavior?

It'd be good to include some advice for increasing hardware resources available to GitHub Enterprise Server instances on Google Cloud Platform.

How is the old or inaccurate behavior currently documented?

"Increasing CPU or memory resources" only addresses GitHub Enterprise Server instances hosted on AWS, Azure, KVM, and VMware. It'd be nice to include instructions for increasing resources for instances hosted on Google Cloud Platform, or at least write a blurb at the top of the page with any known limitations or high-level instructions. (We link to this article from the various articles on installing GitHub Enterprise Server, so right now, administrators on Google Cloud Platform might end up at this article, but they won't see any instructions for their hypervisor.)

Who does this affect?

Administrators of GitHub Enterprise Server using Google Cloud Platform.

What is the impact to users?

Folks might contact support for instructions. Since GitHub doesn't own Google Cloud Platform, sometimes we then have to point the customer to other documentation, so it's potentially a frustrating adventure to find the information that you need for upgrading the virtual machine you're running 😅

Content design and implementation (for Docs Content team members only)

Item	Core	DSP	Ecosystem/API
Content design plan

Short plan linked here

[mattpollard]

We've since documented this process for Azure, but not for Google Cloud Platform. I've adjusted the title and description to reflect that! 🔍

[mattpollard]

We need to flesh this out a bit. I've asked internally to see if we have any examples of this procedure that we can use to write the docs 👀

[mattpollard]

Here's a short plan for these changes:

1. In "Increasing CPU or memory resources", create a new section called "Adding CPU or memory resources for Google Cloud Platform".

2. Within the new section, add three sub-sections:

   • "Resizing considerations for Google Cloud Platform", which should have a short introduction and unordered list identical to the section on Microsoft Azure (one item about scaling with CPUs, and another about assigning a static "external IP address" (Google's terminology)
   • "Supported Google Cloud Platform instance sizes", which should have explanatory text, a note, and a recommendation for a memory-optimized VM
   • "Resizing for Google Cloud Platform", which should mention that it's not possible to add CPU or memory resources, like AWS, and then provide the same four steps (stop, change type, start, SSH in to verify).

[mattpollard]

@cmwilson21 👋🏻 This should be ready for someone to pick up!

[CBID2]

@cmwilson21 👋🏻 This should be ready for someone to pick up!

Hi @mattpollard! :) I created a PR for this issue. It's #30714. I'd love to have your feedback on it. :)

[mattpollard]

Hi, @CBID2 👋🏻 Thanks for the heads up, and the contribution 🤩 Per the body of your PR and your comment about the introduction, I've provided a little initial feedback in #30714 (review).

[CBID2]

I guess you don’t need this anymore @mattpollard

[nguyenalex836]

@CBID2 This might have been closed via our automation - I'll go ahead and reopen for now 💛

[CBID2]

Hi @mattpollard. I decided to not work on this issue anymore.

[mattpollard]

Gotcha 🙇🏻 No worries... thanks for giving it a shot, and for letting us know!