• Figure out how to use the container CI builds for us automatically.
• Possibly use testplatform's implementation of Hive ClusterPools to get a hot cluster to install sippy onto and test against. There will be examples of other projects doing this.
• Launch a postgres container.
• Run a prow import for 4.12.
• Launch the sippy server.
• Launch the sippy UI.
• Run some basic sanity checks against the API to ensure everything came up ok.
• Do some basic curls against sippy UI to ensure it's healthy.

Repeat for kube sippy but as a separate job. This would help us cut down on a lot of mistakes.