incubator-heron icon indicating copy to clipboard operation
incubator-heron copied to clipboard

WIP: Add k8s integration tests to CI

Open Code0x58 opened this issue 5 years ago • 2 comments

I'm aiming to get the integration tests to also run for a kuberentes cluster, currently rough progress for this is in ./scripts/travis/k8s.sh. I'm sharing this as a draft to ask for pointers.

So far the script ensures there is a test image (debian10 isn't working due to the TLS issue), then creates a kind cluster using the ./deploy/kubernetes/minikube/*.yaml which it waits for before starting the integration tests. The cluster looks ok on the surface as the services appear healthy, and topologies can be created and their pods run (ignoring when resource requests are too high at the moment).

The problems I'm seeing at the moment are that topology-test-runner instance state results are not written back to the HTTP collector on the host, which is accessible from the executors from the host URL passed to the test script, and http://127.0.0.1:8080 on the host.

The topology structure is also not updated for topology-test-runner and test-runner. Zookeeper within the cluster is accessible on zookeeper:2181, and 127.0.0.1:2181 from the host.

I suspect this is down to misconfiguration, maybe something like needing separate ~/.heron/conf/kubernetes/*.yaml copies, one for within the cluster, one for the host.

Once that's worked out, I'll clean up and refactor the ./scripts/travis/*.sh test scripts and make a proper PR

Code0x58 avatar Jul 09 '20 23:07 Code0x58

Do we plan to do anymore work on this PR?

joshfischer1108 avatar May 09 '22 13:05 joshfischer1108

Attempt to resolve the merge conflicts with changes from master to check what state the PR is in.

surahman avatar May 09 '22 18:05 surahman