Add note about collecting from Kubernetes Pods

[clayton-cornell]

PR Description

In this PR:

• Minor markdown cleanup
• Add note about only collecting from Kubernetes Pods, not from Nodes.

Which issue(s) this PR fixes

#431

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[mattdurham]

lgtm

[mattdurham]

I am a bit surprised we prefer contractions!

[clayton-cornell]

We generally follow the Google Developer's style guide (with a few modifications as documented in the Writer's Toolkit). Contractions are preferred as outlined here: https://developers.google.com/style/contractions

Quoting the guideline: "In general, we write our documentation in an informal tone, so we recommend using most types of contractions."

[github-actions]

The backport to release/v1.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-1972-to-release/v1.0 origin/release/v1.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x b558c01237c16536f46e8cdafdebde9156da158b
# Push it to GitHub
git push --set-upstream origin backport-1972-to-release/v1.0
git switch main
# Remove the local backport branch
git branch -D backport-1972-to-release/v1.0

Then, create a pull request where the base branch is release/v1.0 and the compare/head branch is backport-1972-to-release/v1.0.

[github-actions]

The backport to release/v1.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-1972-to-release/v1.1 origin/release/v1.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x b558c01237c16536f46e8cdafdebde9156da158b
# Push it to GitHub
git push --set-upstream origin backport-1972-to-release/v1.1
git switch main
# Remove the local backport branch
git branch -D backport-1972-to-release/v1.1

Then, create a pull request where the base branch is release/v1.1 and the compare/head branch is backport-1972-to-release/v1.1.

[github-actions]

The backport to release/v1.2 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-1972-to-release/v1.2 origin/release/v1.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x b558c01237c16536f46e8cdafdebde9156da158b
# Push it to GitHub
git push --set-upstream origin backport-1972-to-release/v1.2
git switch main
# Remove the local backport branch
git branch -D backport-1972-to-release/v1.2

Then, create a pull request where the base branch is release/v1.2 and the compare/head branch is backport-1972-to-release/v1.2.

[github-actions]

The backport to release/v1.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-1972-to-release/v1.3 origin/release/v1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x b558c01237c16536f46e8cdafdebde9156da158b
# Push it to GitHub
git push --set-upstream origin backport-1972-to-release/v1.3
git switch main
# Remove the local backport branch
git branch -D backport-1972-to-release/v1.3

Then, create a pull request where the base branch is release/v1.3 and the compare/head branch is backport-1972-to-release/v1.3.