Steeve Morin

Exactly. If it's already build on the local docker instance, it will be available to the local k8s cluster (in the case of docker for mac/windows). So not only needs...

I do want `kubectl` to be called. However, it should basically run `docker load image.tar.gz` instead of pushing the image to the registry. And indeed use call `kubectl` to run...

Indeed a custom resolver might do the trick !

I'm using Docker for Mac's own kubernetes integration: https://blog.docker.com/2018/01/docker-mac-kubernetes/ Also, running a local registry should pretty wasteful with the image living twice on the disk, I think?

Indeed you're right about the living twice. Thinking about it, why is doing a custom `docker load` resolver (could live outside this repo) a bad design?

@xingao267 most welcome! that said, I'm not sure where to put the test ? also, I'm on macos, and test-e2e-local runs on linux only :(

In rules_k8s, it is possible to override the `kubectl` binary https://github.com/bazelbuild/rules_k8s/tree/master/toolchains/kubectl#download-a-custom-kubectl-binary: ```python load("@io_bazel_rules_k8s//toolchains/kubectl:kubectl_configure.bzl", "kubectl_configure") kubectl_configure( name = "k8s_config", kubectl_path = "@myrepo//my:kubectl", ) ``` This has the advantage for easy swapping...

Bazel 0.21 fails on Android with: ``` ERROR: /Users/steeve/XXX/BUILD.bazel:42:1: in deps attribute of android_library rule //XX/XXX:android_library_base: android_library will be deprecating the use of deps to export targets implicitly. Please use...

Is it a regression though? It makes sense to do this since, if not, include paths will be different wether the code is compiled from the main workspace or via...

I figure I’d get some feedback before going all the way.