Fleet managed K8S resources should match standalone resources #2288
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
cmacknz
added
Team:Cloudnative-Monitoring
cmacknz
requested review from
gsantoro and
devamanv
and removed request for
a team
|
The current set of standalone resource requests for reference: elastic-agent/deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml Lines 716 to 721 in 1c8cc0f |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
🌐 Coverage report
|
|
hey @cmacknz thanks for the PR, would you mind applying the same change at the following places I'm sorry that there are so many places where those limits needs changing. We are working on it. |
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different.
cmacknz
force-pushed
the
synchronize-fleet-standalone-mem-requests
branch
from
1c8cc0f
to
f4cb64e
Compare
gsantoro
approved these changes
Feb 16, 2023
|
/test |
mergify bot
pushed a commit
that referenced
this pull request
Feb 16, 2023
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different. (cherry picked from commit 9c6c5ae)
mergify bot
pushed a commit
that referenced
this pull request
Feb 16, 2023
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different. (cherry picked from commit 9c6c5ae) # Conflicts: # dev-tools/kubernetes/base/elastic-agent-managed/daemonset.yaml
cmacknz
added
backport-v8.6.0
This was referenced Feb 16, 2023
cmacknz
added a commit
that referenced
this pull request
Feb 16, 2023
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different. (cherry picked from commit 9c6c5ae)
cmacknz
added a commit
that referenced
this pull request
Feb 16, 2023
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different. (cherry picked from commit 9c6c5ae)
cmacknz
added a commit
that referenced
this pull request
Feb 16, 2023
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different. (cherry picked from commit 9c6c5ae)
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.
The CPU and memory requests for a standalone agent were updated to higher values than what is currently used for Fleet managed agents. Update the managed configuration to match the standalone configuration there is no reason for them to be different.