delightful-alarm-89564
11/29/2022, 8:48 AMkubectl versionClient Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"windows/amd64"} Unable to connect to the server: dial tcp 10.250.5.174:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
sticky-summer-13450
11/29/2022, 10:09 AM--image-pull-policy=Never
then how is the image going to be pulled to your kubernetes (Rancher Desktop) cluster?delightful-alarm-89564
11/29/2022, 10:33 AMsticky-summer-13450
11/29/2022, 11:05 AMnerdctl
or the docker
instructions?delightful-alarm-89564
11/29/2022, 11:05 AMsticky-summer-13450
11/29/2022, 11:07 AMdocker build --tag...
should have made the image available to your cluster. Let me just replicate the process...delightful-alarm-89564
11/29/2022, 11:07 AMsticky-summer-13450
11/29/2022, 11:18 AMkubectl config get-contexts
just to check your kubectl config is pointing to your local Rancher Desktop context.
$ kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
* rancher-desktop rancher-desktop rancher-desktop
delightful-alarm-89564
11/29/2022, 11:20 AMsticky-summer-13450
11/29/2022, 11:23 AM$ kubectl get pods
NAME READY STATUS RESTARTS AGE
hello-world 1/1 Running 0 52s
dockerd (moby)
delightful-alarm-89564
11/29/2022, 11:27 AMsticky-summer-13450
11/29/2022, 11:27 AMdelightful-alarm-89564
11/29/2022, 11:28 AMsticky-summer-13450
11/29/2022, 12:37 PMdelightful-alarm-89564
11/29/2022, 12:38 PM