The PR changes the behavior of run_kubernetes to not ensure that the locations of the fv3config.yml and the output directory are remote. This assumption is too stringent. run_k8s should be able to use fv3configs stored in the container's file system and save to arbitrary locations (including ones in the container's filesystems or k8s local volume that is mounted).
Also fix a bug when generating the container name for docker images with an "" in them. K8s does not allow "" in the name of container.
The PR changes the behavior of
run_kubernetesto not ensure that the locations of the fv3config.yml and the output directory are remote. This assumption is too stringent. run_k8s should be able to use fv3configs stored in the container's file system and save to arbitrary locations (including ones in the container's filesystems or k8s local volume that is mounted).Also fix a bug when generating the container name for docker images with an "" in them. K8s does not allow "" in the name of container.