Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

kibana: fixed bogus request of 500 millibytes mem #268

Merged
merged 3 commits into from
Sep 19, 2019
Merged

kibana: fixed bogus request of 500 millibytes mem #268

merged 3 commits into from
Sep 19, 2019

Conversation

accek
Copy link
Contributor

@accek accek commented Aug 31, 2019

  • Chart version not bumped (the versions are all bumped and released at the same time)
  • README.md updated with any new values or changes
  • Updated template tests in ${CHART}/tests/*.py
  • Updated integration tests in ${CHART}/examples/*/test/goss.yaml

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@accek accek changed the title Accek patch 2 kibana: fixed bogus request of 500 millibytes mem Aug 31, 2019
Copy link
Contributor

@Crazybus Crazybus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Nice catch! Do you know if 500m is also invalid? My best bet is that the regex matched correctly because it is a valid way for CPU to be specified:

error: deployments.extensions "ea-kibana-kibana" could not be patched: quantities must match the regular expression '^([+-]?[0-9.]+)([eEinumkKMGTP]*[-+]?[0-9]*)$'

@Crazybus
Copy link
Contributor

jenkins test this please

@Crazybus
Copy link
Contributor

jenkins test this please

@accek
Copy link
Contributor Author

accek commented Sep 18, 2019

LGTM!

Nice catch! Do you know if 500m is also invalid?

500m is theoretically valid for memory, but useless. It is accepted by k8s and means 0.5 bytes (half a byte).

@Crazybus Crazybus merged commit 1794dff into elastic:master Sep 19, 2019
@Crazybus
Copy link
Contributor

Thanks for clarifying! Now it makes sense why it never got caught.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants