[FOLIO-2437] update module-kubernetes role Created: 29/Jan/20 Updated: 03/Jun/20 Resolved: 29/Jan/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | Ian Hardy | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: sprint 80/81 |
| Development Team: | Core: Platform |
| Description |
|
module-kubernetes role is still looking to "metadata" and applying defaults (since the metadata section isn't used anymore). Mostly this works OK, but needs updating to pick up newer memory configurations. |
| Comments |
| Comment by Ian Hardy [ 29/Jan/20 ] |
|
fyi David Crossley and John Malconian, I made a few decisions on memory management kubernetes pods since the launch descriptors now use a percentage of the container memory limit for the heap size I've tried to recreate this in k8s: spec:
containers:
...
resources:
limits:
memory: "357913941"
requests:
memory: "236223201"
I'm taking the limit from the launchDescriptor and setting it as the memory limit, and multiplying it by .66 for the requested memory. Requested memory is supposed to help w/scheduling the pods in kubernetes. Handy article: https://cloud.google.com/blog/products/gcp/kubernetes-best-practices-resource-requests-and-limits |