In our recent discussions surrounding testing, we will not (at this time) be automating/testing the actual Kubernetes deployment.

We will, however, need a staging server on which to execute our tests. The CI system will execute the actual test cases against the staging server, which could be either a single-node or multi-node setup.

Optionally, we may need at least one test user registered on this system. This could be avoided if we can figure out how to mock e-mail verification or otherwise automate the registration process (perhaps TravisCI can use ndslabsctl?), but that work is outside of the scope of this ticket.

This ticket is complete when a staging server has been created for use in testing.