Prometheus PVE Exporter: Rightsizing RAM and Disk

[andygrunwald]

✍️ Description

This PR is rightsizing the Prometheus PVE Exporter resources RAM and Disk.

🔗 Related PR / Discussion / Issue

None

✅ Prerequisites

Before this PR can be reviewed, the following must be completed:

• Self-review performed – Code follows established patterns and conventions.
• Testing performed – Changes have been thoroughly tested and verified.

🛠️ Type of Change

Select all that apply:

• [] 🆕 New script – A fully functional and tested script or script set.
• 🐞 Bug fix – Resolves an issue without breaking functionality.
• [] ✨ New feature – Adds new, non-breaking functionality.
• [] 💥 Breaking change – Alters existing functionality in a way that may require updates.

📋 Additional Information (optional)

[github-actions]

⚠️ The script ct/prometheus-pve-exporter.sh failed with the following message:

Failure in line 24 while executing command 'apt-get install -y python3 python3-pip'

[michelroegl-brunner]

You are sure 128MB of Ram are enough so that the install dose not take ages?

[CrazyWolf13]

agreed, 128MB seems too low, I'd rather go with 512 at minimum, if someone really is that low on RAM, one can manually change it later on.

About the disk, thanks!

[MickLesk]

I can live with 512. Less only for alpine.
Its just an "Maximum", the LXC Take what it need

[andygrunwald]

You are sure 128MB of Ram are enough so that the install dose not take ages?

It was not known to me that install speed is a metric that is taken into account in this project. For me, this metric is less relevant as installation is a one time action.

I set the RAM to 512, as this seem to be the outcome of the discussion.

[tremor021]

Ultimately it doesnt really matter unless you're installing some really RAM hungry app. 512MB is a good measure here, you really cant tell if the app gets stupid and spikes RAM usage.