Remove explicit mention of t4g.nano
What does this MR do?
This removes an explicit mention of the t4g.nano
instance in the Autoscaling docker+machine
docs.
This mention came from a user contribution last year - and is a great suggestion for making use of an inexpensive, limited memory, better-vCPU instance for the Runner manager - however, the t4g
series of instances are Graviton instances, which require the use of a arm64
architecture OS - which can be confusing to select from Amazon's standard AMI's.
The previous recommendation was a t2.micro
. I'm on the fence about whether an explicit example for an instance is useful here - it essentially becomes a recommendation, and I think it might be better to leave this with a Customer's own infrastructure standards for the smallest instance they feel like they want to use.
I also changed "standard cost" to "only host with an ongoing baseline cost" - "standard cost" was confusing to me.
Related issues
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course -
Follow the: -
Ensure that the product tier badge is added to topic's h1
. -
Request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are only adding documentation, do not add any of the following labels:
~"feature"
~"frontend"
~"backend"
~"bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set.