Lower disk space eviction limits for network conformance inttest

[twz123]

Description

Recently, the network conformance inttest has been failing regularly. This is because the sonobuoy pods are being evicted when the available disk space on the GitHub runners falls below the default eviction limits. Mitigate this by lowering the eviction limits.

This is a duct-tape solution. It's unclear whether the reduced amount of free disk space on the GitHub runners is due to changes made by GitHub or to changes in k0s.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings