[k8sclusterreceiver]: Update the receiver.k8sclusterreceiver.reportCpuMetricsAsDouble feature gate
#9367
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jvoravong
force-pushed
the
k8sclusterreceiver-feature-gate
branch
from
0b899ba
to
103441c
Compare
dmitryax
reviewed
Apr 20, 2022
dmitryax
approved these changes
Apr 20, 2022
jvoravong
force-pushed
the
k8sclusterreceiver-feature-gate
branch
from
cb11c69
to
bccdb42
Compare
…te is now enabled by default
jvoravong
force-pushed
the
k8sclusterreceiver-feature-gate
branch
from
bccdb42
to
dae07ac
Compare
dmitryax
added
the
ready to merge
bogdandrutu
approved these changes
Apr 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Moving the receiver.k8sclusterreceiver.reportCpuMetricsAsDouble feature gate from its Alpha stage to its Beta stage for release v0.50.0. The feature gate will now be enabled by default.
Link to tracking Issue:
This is small PR, so I did not create a new issue.
Here is the original related issue: #8245
Testing:
All the functionality was tested in the original related issue.
Documentation:
Updated the README notes to include more information.