crosscloudci/cross-cloud

Build better e2e test for CoreDNS (possibly remove Dockerfile + ./e2e/ from ci-* branches)

hh opened this issue · 2 comments

hh commented
Build better e2e test for CoreDNS (possibly remove Dockerfile + ./e2e/ from ci-* branches)
fturib commented

What are the e2e tests ran for CoreDNS in CrossCloudCI Project ?

NOTE: we met during KubeCon at SIG cross-cloud ci meeting, and we agreed to continue that conversation using an Issue in this project.
As I see this issue about the same subject still open, I piggy back on this issue.

My first questions I have are:

  1. What e2e tests are you triggering for the CoreDNS project ?

    • Question below this one is: how can we organize our e2e tests so they are periodically ran by CrossCloudCI.
    • How/where do we define e2e tests that will be ran by CrossCloudCI.
    • Is there some sample to follow to understand the environment ?
    • We have some e2e tests that concerned CoreDNS only, some others that concern CoreDNS as a DNS Server for K8s.

  2. Is there a way to trigger a CrossCloudCI e2e test on coredns from a simple word in the Gighub PR (let say something like : /e2e).