9db5ded1e7
Otherwise for k8s >= 1.26 it fails with: kuryr-pod-1568568478 is forbidden: violates PodSecurity Change-Id: I5593c78b6809b945fa690c723525bc8b6473c58f Depends-On: I7a51b3553a17c21160f76e527a61ef829610a888 |
||
---|---|---|
.. | ||
__init__.py | ||
base_network_policy.py | ||
base.py | ||
consts.py | ||
README.rst | ||
test_annotation_project.py | ||
test_cross_ping_multi_worker.py | ||
test_cross_ping.py | ||
test_daemon.py | ||
test_ha.py | ||
test_kuryr_restart.py | ||
test_namespace.py | ||
test_network_policy.py | ||
test_npwg_multi_vif.py | ||
test_port_pool.py | ||
test_service.py |
What are these tests?
As stated in the tempest developer guide, scenario tests are meant to be used to test the interaction between several OpenStack services to perform a real-life use case.
In the case of the Kuryr Tempest Plugin it also involves interaction with Kubernetes pods, so its manager class includes handlers to its python bindings.
A developer using this manager would be able to perform, among others, CRUD operations with pods, alongside Kuryr-K8s added funcionality.