container: add CSI attributes

[gdvalle]

Fixes #1119

Changes

Add CSI (Container Storage Interface) attributes: container.csi.plugin.name and container.csi.volume.id.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

---

xref open-telemetry/opentelemetry-collector-contrib#32055 (comment)

[joaopgrassi]

Make sure to update things via the make targets:

make fix
make generate-gh-issue-templates

[gdvalle]

I ran into a couple little snags:

• ci: fix makefile docker ownership #1386 fixes the volume UID/GID mappings for the makefile containers.
• ci: sort with dictionary mode for compatibility #1388 A difference between BSD sort and GNU sort defaults. The get-registry-areas.sh script just calls sort, but apparently an OSX/BSD user committed up the current one, which puts cloudevents after cloud. With GNU sort, it's the other way.

[lmolkova]

/cc @open-telemetry/semconv-container-approvers @open-telemetry/semconv-k8s-approvers

[lmolkova]

LGTM!

[lmolkova]

@jmacd could you please take another look? I believe your feedback is addressed.

[ChrsMark]

Hey @gdvalle, is there a reason why those were only added in the registry and not as Resource Attributes as well?
In https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32055/files#diff-3343de7bfda986546ce7cb166e641ae88c0b0aecadd016cb253cd5a0463ff464R72-R79 I see they are added as Resource Attributes but from the SemConv perspective that's not clear yet, right? So I wonder if we can actually use them in the implementations right now.

[gdvalle]

Hey @gdvalle, is there a reason why those were only added in the registry and not as Resource Attributes as well? In https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32055/files#diff-3343de7bfda986546ce7cb166e641ae88c0b0aecadd016cb253cd5a0463ff464R72-R79 I see they are added as Resource Attributes but from the SemConv perspective that's not clear yet, right? So I wonder if we can actually use them in the implementations right now.

No, just my oversight. See #1499 for adding to resource attributes.