What's the recommended Disk Space for CodeSpaces?

[rido-min]

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy AIO to CodeSpaces

Any log messages given by the failure

Expected/desired behavior

CodeSpaces is configured with enough Memory and Disk

OS and Version?

CodeSpaces

Versions

Public Preview

[rido-min]

I found how to clean disk space in codespaces, however the k3d node is evicting most of the pods because it reports as DiskPressure.

I think the k3d cluster needs to be configured with appropriate disk space to handle the AIO deployment and additional workloads.

[jlian]

We have a minimum codespace deployment storage set as 32GB which in my experience should be enough

explore-iot-operations/.devcontainer/devcontainer.json

Lines 10 to 14 in 9f4bef4

	"hostRequirements": {
	"cpus": 4,
	"memory": "8gb",
	"storage": "32gb"
	},

I've seen the low space issue before and it was never clear what causes it since it goes away when I do a full codespace rebuild.

Are you seeing this happen on a completely fresh deployment, or sometime afterwards?

[rido-min]

I have seen this behavior more than once in a fresh deployment, I'd say 32Gb is not enough once ARC and AzMonitor are enabled in the cluster.

[jlian]

Hmm ok. It's easy for me to change the default to be 64GB. You can also resize your codespace in the UI https://docs.github.com/en/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace

[ryanwinter]

What happened to increasing this? I see you closed the PR @jlian