Migrate antithesis to K8s

[serathius]

Ref #20572

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.43%. Comparing base (5aebee8) to head (2b2ea29).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

see 21 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #21541      +/-   ##
==========================================
- Coverage   68.45%   68.43%   -0.02%     
==========================================
  Files         428      428              
  Lines       35383    35383              
==========================================
- Hits        24221    24215       -6     
- Misses       9761     9767       +6     
  Partials     1401     1401              

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5aebee8...2b2ea29. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[serathius]

Run failed. @marcus-hodgson-antithesis said you need to change test type from Basic_test to Basic_k8s_test. However I don't see any place to switch that in https://github.com/antithesishq/antithesis-trigger-action

https://linuxfoundation.antithesis.com/report/AoQZ2hpIiK3E7UbJyV07QSlI/C2-sYK3t03a972_AYuITfbl-zs2alU4dUUDt468U2hM.html?auth=v2.public.eyJuYmYiOiIyMDI2LTAzLTI5VDEyOjQ1OjM5LjU1MTUzMTQwOVoiLCJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0IjoiQzItc1lLM3QwM2E5NzJfQVl1SVRmYmwtenMyYWxVNGRVVUR0NDY4VTJoTS5odG1sIiwicmVwb3J0X2lkIjoiQW9RWjJocElpSzNFN1ViSnlWMDdRU2xJIn19fae0UN_83uQ2YxT5gG9lkJu3fhuVGDrNgQeHjsVShC0MydVmH-wZ2cGpYLSi58uwkigwfAPF776TLr8hO82yowo

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nwnt, serathius

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [serathius]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[serathius]

We have a passing run https://linuxfoundation.antithesis.com/report/gnMFNSkbTUOkpLxqq7y_vP-l/oQYD0X8p0pl3UkSCmRM-6b0L8McEnD0St5u351n-iKw.html?auth=v2.public.eyJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0Ijoib1FZRDBYOHAwcGwzVWtTQ21STS02YjBMOE1jRW5EMFN0NXUzNTFuLWlLdy5odG1sIiwicmVwb3J0X2lkIjoiZ25NRk5Ta2JUVU9rcEx4cXE3eV92UC1sIn19LCJuYmYiOiIyMDI2LTAzLTI5VDIwOjA2OjUyLjM1NDAyMjE4NFoifbIaxbqyCV__bSDACYGii7iPrj-1nSJKH9zfFm3vd0YSkNYdHaRKQQYz_iRrGumWp3Kv_mfL6hm0r_MH8J8BjwY

It confirmed that antithesis.duration still accepts hours and not minutes.

To confirm with previous docker-compose runs, it didn't report following assertion errors:

• container: etcd1, exit code: 1 - that's good, we don't care about this one
• consistent_index isn't equal to snapshot index - could imply different failure injection and worse exploration?
• Linearization timeout - could imply less aggressive failure injection, but might show up if we increase test duration.

cc @marcus-hodgson-antithesis could you help review this migration, and also ask someone else from Antithesis that specializes in K8s to take a look too? Would be good to confirm that we will not regress our ability to reproduce issues.

[marcus-hodgson-antithesis]

@serathius the basic-k8s-test kubernetes endpoint only runs with network faults. The container faults / other faults that we currently have enabled on the docker setup, haven't been enabled yet on this kubernetes one.

I'm in the process of creating a custom endpoint for etcd where we can enable move over what we have from the current setup to this new one