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

allow cpu/mem requests and limits to be set globally in the injector #235

Merged

Conversation

joemiller
Copy link
Contributor

Adds new flags and env vars to the injector config that allow changing the cpu/mem
requests and limits of the injected containers:

  • -cpu-request / AGENT_INJECT_CPU_REQUEST
  • -cpu-limit / AGENT_INJECT_CPU_LIMIT
  • -mem-request / AGENT_INJECT_MEM_REQUEST
  • -mem-limit / AGENT_INJECT_MEM_LIMIT

closes #216
closes #166

@joemiller joemiller marked this pull request as ready for review March 19, 2021 23:28
@joemiller
Copy link
Contributor Author

Is there documentation I should update as well?
thanks!

@jasonodonnell jasonodonnell self-requested a review April 2, 2021 15:23
@jasonodonnell
Copy link
Contributor

@joemiller I will update the documentation, thank you!

Copy link
Contributor

@jasonodonnell jasonodonnell left a comment

Choose a reason for hiding this comment

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

Hi @joemiller, thanks for the contribution! This looks great but can you add these environment variables to the deploy/deployment.yaml file?

@jasonodonnell
Copy link
Contributor

Once that's added I'll approve this and merge @joemiller. Thanks again!

@joemiller joemiller force-pushed the request-limits-global-config branch from d61c1b2 to 87445be Compare April 2, 2021 17:26
@joemiller
Copy link
Contributor Author

@jasonodonnell updated the deploy/injector-deployment.yaml with the 4 new env vars

Adds new flags and env vars to the injector config that allow changing the cpu/mem
requests and limits of the injected containers:

- `-cpu-request` / `AGENT_INJECT_CPU_REQUEST`
- `-cpu-limit` / `AGENT_INJECT_CPU_LIMIT`
- `-mem-request` / `AGENT_INJECT_MEM_REQUEST`
- `-mem-limit` / `AGENT_INJECT_MEM_LIMIT`
@joemiller joemiller force-pushed the request-limits-global-config branch from 87445be to 5c045d6 Compare April 2, 2021 17:41
Copy link
Contributor

@jasonodonnell jasonodonnell left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@jasonodonnell jasonodonnell merged commit f524d14 into hashicorp:master Apr 2, 2021
NLRemco pushed a commit to NLRemco/vault-k8s that referenced this pull request Feb 22, 2022
…ashicorp#235)

Adds new flags and env vars to the injector config that allow changing the cpu/mem
requests and limits of the injected containers:

- `-cpu-request` / `AGENT_INJECT_CPU_REQUEST`
- `-cpu-limit` / `AGENT_INJECT_CPU_LIMIT`
- `-mem-request` / `AGENT_INJECT_MEM_REQUEST`
- `-mem-limit` / `AGENT_INJECT_MEM_LIMIT`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change defaults for agent sidecar requests and limits Custom Vault agent container resource defaults
2 participants