You don’t upload images directly to a cluster. They must be uploaded to a container registry (IBM has their own if you want to use that), and then they are pulled by down by nodes in the cluster.
There is an option how you could move images or even better directly build your image on the Kubernetes cluster:
A key feature of BuildKit CLI for kubectl is that it strives to make the images you build immediately available in the container runtime of your Kubernetes cluster so you can “bounce” your pod(s) to pick up a freshly built image with virtually no overhead.
In this post I present a method on how to boost developers productivity the BuildKit CLI for kubectl proving that developers can cut down deployment time significantly while staying in the inner-loop.
