[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

[openshift-cherrypick-robot]

This is an automated cherry-pick of #523

/assign periklis

[openshift-ci-robot]

@openshift-cherrypick-robot: Detected clone of Bugzilla bug 1886856 with correct target release. Retitling PR to link to clone:
/retitle [release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

In response to this:

[release-4.6] Bug 1886856: Increase es proxy default memory resources to 256Mi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1880960, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1886856 is in the state MODIFIED, which is one of the valid states (MODIFIED, VERIFIED)
• dependent Bugzilla bug 1886856 targets the "4.7.0" release, which is one of the valid target releases: 4.7.0
• bug has dependents

In response to this:

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[periklis]

/lgtm

[periklis]

/retest

[alanconway]

/uncc @alanconway

[ewolinetz]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ewolinetz, openshift-cherrypick-robot, periklis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ewolinetz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[periklis]

/cherry-pick release-4.5

[openshift-cherrypick-robot]

@periklis: once the present PR merges, I will cherry-pick it on top of release-4.5 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[periklis]

/bugzilla refresh

[openshift-ci-robot]

@periklis: This pull request references Bugzilla bug 1880960, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.z) matches configured target release for branch (4.6.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1886856 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
• dependent Bugzilla bug 1886856 targets the "4.7.0" release, which is one of the valid target releases: 4.7.0
• bug has dependents

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ecordell]

How are the limits decided / how does it scale? Are they dependent on elasticsearch load?

[periklis]

How are the limits decided / how does it scale? Are they dependent on elasticsearch load?

These values are not dependent on how elasticsearch handles load. These values are based on load testing by fluentd requests to elasticsearch via this proxy. The load parameters were to sustain 50rps, which is this usual load and leave room for 100rps in edge cases, e.g. clusters with a high amount of cluster nodes. Although a 100rps scenario results in a bigger ES cluster with more than the typical 3 nodes and requires a bigger infra nodes pool.

[openshift-ci-robot]

@openshift-cherrypick-robot: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/cluster-logging-operator#740 is open

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 1880960 has not been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@periklis: new pull request created: #582

In response to this:

/cherry-pick release-4.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.