You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest the following changes to the integration test:
Create a namespace and run tests that create objects against that namespace - this allows for the namespace to be deleted in a module levelon_exit callback, thus ensuring everything is cleaned up.
Use the alpine image for the pod that is created rather than obmarg/health-proxy as alpine is small and will be pulled quickly.
Do not assume there are no ClusterRoles in the test RBAC Authorization V1 Beta 1 API as this depends on having a fresh K8S installation.
The text was updated successfully, but these errors were encountered:
Re: 1. - Would it make sense to create a unique namespace for each tests (using a uuid as the name or something). That way integration tests can continue to run async without interfering with each other...
I suggest the following changes to the integration test:
on_exit
callback, thus ensuring everything is cleaned up.alpine
image for the pod that is created rather thanobmarg/health-proxy
asalpine
is small and will be pulled quickly.ClusterRoles
in the testRBAC Authorization V1 Beta 1 API
as this depends on having a fresh K8S installation.The text was updated successfully, but these errors were encountered: