Currently the k8s-env command runs a teraslice image with the tag teraslice-workspace:e2e. This works well for development, as an image is built with that tag at the beginning of the script. If someone wishes to run a different teraslice image they must first re-tag that image in their local registry with teraslice-workspace:e2e and pass in the skip-build flag, so the image isn't overwritten.
Adding a new flag such as teraslice-image would allow you to run any version of teraslice you have an image of, without having to pull down the code locally and build.
Currently the
k8s-envcommand runs a teraslice image with the tagteraslice-workspace:e2e. This works well for development, as an image is built with that tag at the beginning of the script. If someone wishes to run a different teraslice image they must first re-tag that image in their local registry withteraslice-workspace:e2eand pass in theskip-buildflag, so the image isn't overwritten.Adding a new flag such as
teraslice-imagewould allow you to run any version of teraslice you have an image of, without having to pull down the code locally and build.