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

Seperate resrouces for metricbeat daemonset and deployment #467

Closed
mitchellmaler opened this issue Jan 31, 2020 · 2 comments
Closed

Seperate resrouces for metricbeat daemonset and deployment #467

mitchellmaler opened this issue Jan 31, 2020 · 2 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@mitchellmaler
Copy link

Describe the feature:
Add separate resources variables for the daemonset and the deployment instead of using the same one.

Describe a specific use case for the feature:
Each type of deployment of metricbeat might need different resources where they both do different things in terms of metric collection. Seperating the values could allow someone to add more resources for the deployment but less in the deamonset pods.

@jmlrt jmlrt added the enhancement New feature or request label Feb 3, 2020
@jmlrt
Copy link
Member

jmlrt commented Feb 3, 2020

Hi @mitchellmaler, we have #448 open for that

@jmlrt
Copy link
Member

jmlrt commented Feb 3, 2020

There is also #446 issue so I'll close this one as duplicate and the progress will be tracked on #446 and #448.

@jmlrt jmlrt closed this as completed Feb 3, 2020
@jmlrt jmlrt added the duplicate This issue or pull request already exists label Feb 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants