I had some trouble deploying Spinnaker to Kubernetes due to the host Node running out of memory (OOM killer and Kubernetes is not a happy thing!). I have configured my cluster to auto-scale based on resource requests/limits, but it turns out Halyard doesn’t set any of these by default (https://github.com/spinnaker/spinnaker/issues/1311), so after a little while of seemingly healthy operation, the Node eventually fell over in a heap.
So I looked for a way to specify resource requests and limits and found this link in the above issue report:
This is great!, I thought. I can experiment with various values until I get it right. So I edited ~/.hal/config and applied appropriate requests and limits for each Spinnaker component exactly as described in the doc and ran ‘hal deploy apply’. But when I looked at the resulting ReplicaSets, none of them had any resources set, so I’ve ended up in the same “creaking bridge” situation as before.
Does anyone know how to apply the config changes as specified in that document? I’ve read the docs many, many times looking for clues but am none the wiser.
Can anyone help?