docs: Add resource tags documentation page by promptless[bot] · Pull Request #747 · runpod/docs

promptless · 2026-07-29T20:26:05Z

Open this suggestion in Promptless to view citations and reasoning process

Documents Runpod resource tags, the organization-shared labels users apply to resources to organize, filter, and track usage. The new accounts-billing/resource-tags.mdx page covers supported resource types (Pods, Serverless endpoints, network volumes, templates, and container registry auths), how tags differ from and complement cost centers, the full tag lifecycle (create, attach, filter, update, detach, delete), and best practices. It is added to the "Accounts and billing" navigation group after cost centers.

Trigger Events

Message in Slack channel #topic-documentation: @Promptless Create a draft doc for this request - <https://linear.app/runpod/issue/DOCS-479/ur-resource-taggin...

Review feedback applied (2026-07-31)

Addressing @lavanya-gunreddi's request to reflect @jjmchew's line-7 note about tag key/value rules:

Document that a tag key can be any string except the reserved runpod: prefix, and that the value is optional / may be left blank. — Applied (with minor clarity wording). Added to the opening section, immediately after the "key-value labels" sentence: "A tag key can be any string except one that begins with the reserved runpod: prefix. The tag value is optional and can be left blank." The reviewer's requested facts are both stated verbatim in substance; the key rule was phrased in the singular, active voice for readability rather than as a double negative. The maintainer's other edits (commit 959379f) are preserved unchanged.

Tip: Leave inline comments with @Promptless on suggestion diffs in the Promptless dashboard for targeted refinements 💬

Add accounts-billing/resource-tags.mdx describing organization-shared resource tags and add it to the Accounts and billing nav group.

promptless · 2026-07-29T20:26:07Z

+| Resource type | Description |
+|--------------|-------------|
+| Pods | Tag individual Pods to organize compute resources. |
+| Serverless endpoints | Tag endpoints to group related Serverless workloads. |


Verifies the claim that resource tags and cost centers cover different resource sets. Cost centers' "Supported resources" table lists Pods, Serverless endpoints, Network volumes, and Instant Clusters (no Templates, no Container registry auths), confirming coverage differs from resource tags' five supported types.

Source:

docs/accounts-billing/cost-centers.mdx

Lines 27 to 38 in 7fc37cc

## Supported resources

Cost centers track billable resources across the Runpod platform:

| Resource type | How costs are tracked |

|--------------|----------------------|

| Pods | GPU compute and storage costs are combined into a single Pod charge. |

| Serverless endpoints | All endpoint usage is tracked under the assigned cost center. |

| Network volumes | Storage costs for volumes are tracked separately from compute resources. |

| Instant Clusters | Cluster compute costs are tracked under the assigned cost center. |

Each resource can belong to only one cost center at a time. Resources without an assigned cost center appear as uncategorized.

mintlify · 2026-07-29T20:26:59Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
runpod-docs	🟢 Ready	View Preview	Jul 29, 2026, 8:26 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

mintlify · 2026-07-29T20:29:20Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
runpod-docs	🟡 Building	–	Jul 29, 2026, 8:26 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

jjmchew · 2026-07-30T23:36:21Z

+| Pods | Tag individual Pods to organize compute resources. |
+| Serverless endpoints | Tag endpoints to group related Serverless workloads. |
+| Network volumes | Tag network volumes to track persistent storage. |
+| Templates | Tag templates to organize reusable configurations. |


We have *not added tagging to templates or container registry auth (CRA), yet.
We *have added tagging to Clusters.

@Promptless work on this comment

promptless · 2026-07-30T23:36:25Z

Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.)

jjmchew · 2026-07-30T23:37:53Z

+
+## Create a tag
+
+To create a tag, open the resource tags management area in the Runpod console, give it a name, optionally assign a color, and save it. The new tag then becomes available across your organization for anyone to apply.


We have not implemented coloured tags. This is the first I've heard of this - should it be added as a future ticket/feature?

FYI off-the-top of my head, this will require a db schema update to store tag colour for re-use/consistency.

@Promptless work on this comment

jjmchew · 2026-07-30T23:46:32Z

+
+## Update a tag
+
+You can update a tag to change its name, color, or metadata. Because tags are shared across your organization, updating a tag changes it for every resource that carries it.


"You can update a tag to change it's name (key), and any associated value."

We can't change color and I'm not sure what "metadata" refers to.

@Promptless work on this comment

jjmchew · 2026-07-30T23:51:45Z

+tag: "NEW"
+---
+
+Resource tags are labels you create and apply to your Runpod resources to organize, filter, and track usage across your organization. By tagging resources, you can group them in ways that reflect how your teams, projects, and environments are structured.


I assume this was written when tags were still just a single label (like cost centers)?

Current implementation of tags is a "key: value" pair. Any string can be used for the key except runpod:; any string (including a blank string "") can be used for value (it's optional).

Proposed edit to first sentence:
"Resource tags are key-value labels you create and apply to your ... ".

@Promptless work on this comment

promptless · 2026-07-31T12:09:53Z

Thanks for the review! We're working through your comments now and will update the resource tags page (accounts-billing/resource-tags.mdx) accordingly. We'll follow up here once the revisions are pushed.

promptless · 2026-07-31T12:12:44Z

Update: we've reviewed all the feedback on this page. We're revising the resource tags page to reflect that tags are key-value pairs, correct the taggable resource types (Instant Clusters are now supported; templates and container registry auths are not yet), and remove the colored-tags references. We'll push the updated draft shortly.

…ed resources, remove color, fix update wording

promptless · 2026-07-31T12:24:29Z

Thanks for the detailed review, @lavanya-gunreddi. Going through each comment, all of the requested corrections are already in place on this branch as of commit 959379f:

Tags are now described as key-value labels rather than single labels.
The supported-resources list is corrected: Instant Clusters added; templates and container registry auths removed, along with the backwards cost-centers comparison sentence.
The color option is removed from "Create a tag."
"Update a tag" now reads that you can change its name (key) and any associated value (no color or other metadata).

Since those fixes are already committed, we didn't make any further changes to the page.

One optional detail from James's line-7 note isn't yet reflected: that a tag key can be any string except the reserved runpod: prefix, and that the value is optional and may be left blank. Happy to add that if you'd like it — just let us know.

lavanya-gunreddi · 2026-07-31T14:04:39Z

@Promptless One optional detail from James's line-7 note isn't yet reflected: that a tag key can be any string except the reserved runpod: prefix, and that the value is optional and may be left blank. add this too.

promptless · 2026-07-31T14:05:10Z

Will do — we're adding that now: the tag key can be any string except the reserved runpod: prefix, and the value is optional and may be left blank. We'll follow up here once the update is pushed.

@jjmchew

Per @jjmchew's line-7 review comment (approved by @lavanya-gunreddi): a tag key can be any string except one that begins with the reserved `runpod:` prefix, and the tag value is optional and can be left blank.

promptless · 2026-07-31T14:13:35Z

Done, @lavanya-gunreddi. We've added James's line-7 detail to the resource tags page: a tag key can be any string except one that begins with the reserved runpod: prefix, and the tag value is optional and can be left blank. It's in the page introduction, right after the key-value labels description, and none of your other edits were changed. PR #747 is updated and ready for another look.

Add resource tags documentation page (DOCS-479)

867968e

Add accounts-billing/resource-tags.mdx describing organization-shared resource tags and add it to the Accounts and billing nav group.

promptless Bot commented Jul 29, 2026

View reviewed changes

mintlify Bot deployed to staging July 29, 2026 20:26 View deployment

jjmchew reviewed Jul 30, 2026

View reviewed changes

Fix resource tags per James review: key-value labels, correct support…

959379f

…ed resources, remove color, fix update wording

mintlify Bot deployed to staging July 31, 2026 12:15 View deployment

Merge branch 'main' into promptless/docs-479-resource-tags

3ce2a6f

mintlify Bot deployed to staging July 31, 2026 12:22 View deployment

Add tag key rule and optional value per James's line-7 review

8d0bcb7

Per @jjmchew's line-7 review comment (approved by @lavanya-gunreddi): a tag key can be any string except one that begins with the reserved `runpod:` prefix, and the tag value is optional and can be left blank.

mintlify Bot deployed to staging July 31, 2026 14:12 View deployment

	## Supported resources

	Cost centers track billable resources across the Runpod platform:

	\| Resource type \| How costs are tracked \|
	\|--------------\|----------------------\|
	\| Pods \| GPU compute and storage costs are combined into a single Pod charge. \|
	\| Serverless endpoints \| All endpoint usage is tracked under the assigned cost center. \|
	\| Network volumes \| Storage costs for volumes are tracked separately from compute resources. \|
	\| Instant Clusters \| Cluster compute costs are tracked under the assigned cost center. \|

	Each resource can belong to only one cost center at a time. Resources without an assigned cost center appear as uncategorized.


		## Create a tag

		To create a tag, open the resource tags management area in the Runpod console, give it a name, optionally assign a color, and save it. The new tag then becomes available across your organization for anyone to apply.


		## Update a tag

		You can update a tag to change its name, color, or metadata. Because tags are shared across your organization, updating a tag changes it for every resource that carries it.

Uh oh!

Conversation

promptless Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

promptless Bot Jul 29, 2026

Choose a reason for hiding this comment

Uh oh!

mintlify Bot commented Jul 29, 2026

Uh oh!

mintlify Bot commented Jul 29, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

promptless Bot commented Jul 30, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

promptless Bot commented Jul 31, 2026

Uh oh!

promptless Bot commented Jul 31, 2026

Uh oh!

promptless Bot commented Jul 31, 2026

Uh oh!

lavanya-gunreddi commented Jul 31, 2026

Uh oh!

promptless Bot commented Jul 31, 2026

Uh oh!

promptless Bot commented Jul 31, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

promptless Bot commented Jul 29, 2026 •

edited

Loading