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.

Sign up for GitHub

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

Jump to bottom

Expose cpu/mem limits #73

Merged
merged 1 commit into from
Oct 18, 2023
Merged

Expose cpu/mem limits #73

merged 1 commit into from
Oct 18, 2023

Conversation

hardillb
Copy link
Contributor

part of FlowFuse/flowfuse#2755

Description

Passes the CPU and memory limits to the container (and hence nr-launcher)

Related Issue(s)

FlowFuse/flowfuse#2755

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

  • Backport needed? -> add the backport label
  • Includes a DB migration? -> add the area:migration label

@hardillb hardillb added this to the 1.13 milestone Oct 17, 2023
@hardillb hardillb requested a review from knolleary October 17, 2023 13:56
@hardillb hardillb self-assigned this Oct 17, 2023
@hardillb hardillb changed the title Expose cpu/mem info Expose cpu/mem limits Oct 17, 2023
@hardillb hardillb merged commit 3b1ea2e into main Oct 18, 2023
1 check passed
@hardillb hardillb deleted the expose_limits branch October 18, 2023 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Pezmc Pezmc Pezmc approved these changes

@knolleary knolleary Awaiting requested review from knolleary

Assignees

@hardillb hardillb

Labels
None yet
Projects
None yet
Milestone
1.13
Development

Successfully merging this pull request may close these issues.
2 participants
@hardillb @Pezmc