Skip to content
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

Cherry-pick #12476 to 7.2: Fix 11975 - change Kubernetes container cpu cores fields to float #12609

Merged
merged 2 commits into from
Jun 20, 2019

Conversation

exekias
Copy link
Contributor

@exekias exekias commented Jun 19, 2019

Cherry-pick of PR #12476 to 7.2 branch. Original message:

This is an attempt to fix #11975 where it's reported that the kubernetes.container.cpu.limit.cores and kubernetes.container.cpu.requests.cores fields should be floats instead of longs.

This is my first contribution, so please let me know if I've missed anything. make update has been run and the result committed. If there are other fields that need to be changed along the same lines, I'd be grateful if someone could clue me in.

Thanks in advance for your time :)

…astic#12476)

* Fix 11975 kubernetes cores fields data type long -> float (elastic#11975)

kubernetes.container.cpu.limit.cores is now a float
kubernetes.container.cpu.request.cores is now a float

(cherry picked from commit 8502c79)
@exekias exekias merged commit 9ba65d8 into elastic:7.2 Jun 20, 2019
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…iner cpu cores fields to float (elastic#12609)

* Fix 11975 - change Kubernetes container cpu cores fields to float (elastic#12476)

* Fix 11975 kubernetes cores fields data type long -> float (elastic#11975)

kubernetes.container.cpu.limit.cores is now a float
kubernetes.container.cpu.request.cores is now a float

(cherry picked from commit d8eb8e8)

* Update CHANGELOG.next.asciidoc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants