Implement CPU/memory resource requests

Bug #1915797 reported by Tom Haddon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-k8s-mattermost
Undecided
Unassigned

Bug Description

We should set CPU / memory requests for the discourse pods deployed via the charm.

Upstream has the following: https://mattermost.com/blog/mattermost-installation-for-sysadmins/ (although this doesn't specifically mention deploying in containers, so we'll need to try to figure out the best approach here).

See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more details on this. This will likely need to be implemented via k8s_resources.

Revision history for this message
Tom Haddon (mthaddon) wrote :

This is done via juju constraints, although per https://bugs.launchpad.net/juju/+bug/1919976 there isn't a way to do limits and requests separately.

Changed in charm-k8s-mattermost:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers