Version:
Domino 5.2+
Issue:
If through troubleshooting or just to follow the sizing guide, the CPU/memory requests and/or limits, of a pod need to be changed, you will need to add those changes to your domino.yaml to persist those changes across upgrades and other runs of the installer.
The domino.yaml is the fleetcommand-agent installer configuration file.
During runs of the installer, if the resource settings of pods that have been changed from the default helm charts have not been added to your domino.yaml those sizing changes will be reverted to the defaults when the installer is run again.
The Domino install team will try to find these non default values if they are upgrading, but the easiest way for them to find those is if they are already in the domino.yaml installer configuration file already.
Resolution:
Adding these changes to the domino.yaml is fairly straight forward and should be done whenever live edits are made to the kubernetes objects.
In your domino.yaml file, look for
release_overrides:
If this does not exist, add to it to your domino.yaml. Under this add your resource changes as per the examples below for nucleus and data-plane:
release_overrides:
data-plane: chart_values: agent: deployment: resources: limits: cpu: 4000m memory: 4Gi requests: cpu: 2000m memory: 2Gi nucleus: chart_values: config: javaMaxHeap: 6G keycloak: {} replicaCount: frontend: 3 resources: dispatcher: limits: cpu: 5 memory: 11Gi requests: cpu: 4 memory: 8Gi frontend: limits: cpu: 5 memory: 11Gi requests: cpu: 4 memory: 8Gi
Note that the values here are from the large sizing guide, your values may be larger or smaller. More examples can be found at the large sizing guide.
Comments
0 comments
Please sign in to leave a comment.