-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[processor/k8sattributes] Support name:tag@digest
image name format
#36131
Comments
name:tag@digest
image name formatname:tag@digest
image name format
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This feels correct. The digest can instead be captured in |
@TylerHelmuth indeed, you will get full content of Capturing |
@zarbis I meant fixing the captured fields to
feels the most right |
…36145) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixed issue with `k8sattributesprocessor` where digest is not properly separated from tag if both are present. used official docker library to perform parsing. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #36131 <!--Describe what testing was performed and which tests were added.--> #### Testing unit tests integration/e2e tests <!--Describe the documentation added.--> #### Documentation N/A. Fields are already described correctly, this is simply fixing parsing logic <!--Please delete paragraphs that you did not use before submitting.-->
…pen-telemetry#36145) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixed issue with `k8sattributesprocessor` where digest is not properly separated from tag if both are present. used official docker library to perform parsing. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#36131 <!--Describe what testing was performed and which tests were added.--> #### Testing unit tests integration/e2e tests <!--Describe the documentation added.--> #### Documentation N/A. Fields are already described correctly, this is simply fixing parsing logic <!--Please delete paragraphs that you did not use before submitting.-->
…pen-telemetry#36145) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixed issue with `k8sattributesprocessor` where digest is not properly separated from tag if both are present. used official docker library to perform parsing. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#36131 <!--Describe what testing was performed and which tests were added.--> #### Testing unit tests integration/e2e tests <!--Describe the documentation added.--> #### Documentation N/A. Fields are already described correctly, this is simply fixing parsing logic <!--Please delete paragraphs that you did not use before submitting.-->
Component(s)
processor/k8sattributes
What happened?
Description
For better integrity guarantees we've started using
name:tag@digest
image reference format (e.g.alpine:3.19@sha256:ae65dbf8749a7d4527648ccee1fa3deb6bfcae34cbc30fc67aa45c44dcaa90ee
).It doesn't seem to be part of OCI image spec, but many projects use it (for example Karpenter).
Steps to Reproduce
alpine:3.19@sha256:ae65dbf8749a7d4527648ccee1fa3deb6bfcae34cbc30fc67aa45c44dcaa90ee
k8sattributes
processor:Expected Result
Actual Result
So basically split happens on last colon, not the first one.
Collector version
0.107.0
Environment information
Environment
K8s: 1.29
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: