-
Notifications
You must be signed in to change notification settings - Fork 65
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
[Feature]: New tasks should adopt the configured cfProcessDefaults
#1197
Comments
georgethebeatle
added a commit
that referenced
this issue
Jun 14, 2022
Issue: #1197 Co-authored-by: Georgi Sabev <[email protected]>
georgethebeatle
added a commit
that referenced
this issue
Jun 14, 2022
Issue: #1197 Co-authored-by: Georgi Sabev <[email protected]>
georgethebeatle
added a commit
that referenced
this issue
Jun 15, 2022
Issue: #1197 Co-authored-by: Georgi Sabev <[email protected]>
danail-branekov
added a commit
to cloudfoundry/eirini-controller
that referenced
this issue
Jun 15, 2022
Issue: cloudfoundry/korifi#1197 Co-authored-by: Georgi Sabev <[email protected]>
danail-branekov
added a commit
that referenced
this issue
Jun 15, 2022
This version propagates the disk/memory constraints to the pod template of the cf task job as limits/requests Issue: #1197 Co-authored-by: Georgi Sabev <[email protected]>
Merged
danail-branekov
added a commit
that referenced
this issue
Jun 15, 2022
This version propagates the disk/memory constraints to the pod template of the cf task job as limits/requests Issue: #1197 Co-authored-by: Georgi Sabev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
As a developer
I want to run tasks
So that I can execute one-off workloads
Acceptance Criteria
WHEN I create a task via the Kubernetes API
THEN I I see the task pod has resource limits and requests matching the
cfProcessDefaults
in our configuration:spec.containers[].resources.limits.memory
andspec.containers[].resources.requests.memory
should matchcfProcessDefaults.memoryMB
spec.containers[].resources.limits.ephemeral-storage
andspec.containers[].resources.requests.ephemeral-storage
should matchcfProcessDefaults.diskMB
AND I see the following fields in the task
status
:memoryMB
matchingcfProcessDefaults.memoryMB
diskQuotaMB
matchingcfProcessDefaults.diskMB
WHEN I create a task via the Korifi API shim
THEN I I see all of the above
AND I see the following fields in the response:
memory_in_mb
matchingcfProcessDefaults.memoryMB
disk_in_mb
matchingcfProcessDefaults.diskMB
Dev Notes
eirini-controller
currently ignores thememoryMB
anddiskMB
fields onTask
, so we'll have to fix that for this to work.The text was updated successfully, but these errors were encountered: