ci: cleanup resources after e2e tests

[apricote]

Remove all deployed resources to avoid running into limit errors.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 45.16%. Comparing base (89e3781) to head (a1449b9).
Report is 1 commits behind head on main.

❗ Current head a1449b9 differs from pull request most recent head 7031333

Please upload reports for the commit 7031333 to get more accurate results.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #641   +/-   ##
=======================================
  Coverage   45.16%   45.16%           
=======================================
  Files          12       12           
  Lines        1169     1169           
=======================================
  Hits          528      528           
  Misses        618      618           
  Partials       23       23           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jooola]

Hmm, does the k8s tests cleanup the volumes if the test fail? Because I am not sure if we clean volumes with the terraform module.

[apricote]

We dont, the kubernetes csi tests try to clean those up if possible. I could add a hcloud volume delete $(hcloud volume list -o noheader -o columns=id) after taking down the env. (With a check for empty list)

[jooola]

We dont, the kubernetes csi tests try to clean those up if possible. I could add a hcloud volume delete $(hcloud volume list -o noheader -o columns=id) after taking down the env. (With a check for empty list)

Let's see how that goes, if we stumble on a problem again we'll add the command.