Hi
I'm launching ktunnel with my custom bat which creates non-privileged deployment/svc for ktunnel proxy server and then starts ktunnel.exe with -r
Also ktunnel image is changed to point to my inner docker registry. Beside that the deployment/svc are identical to what ktunnel creates. Ktunnel server starts ok with that deployment/svc.
For some reason I see the second deployment version. It creates a pod that is stuck in tryin to download ktunnel image using its original url. And oc wait waits for this second pod until timeout.
So even before ktunnel.exe itself is called.
Why does this happen? Does ktunnel server create it? And how do I prevent that?
upd: I was wrong about the second deployment being created before ktunnel.exe is called. openshift's terminating pods got me confused. definitely ktunnel.exe makes it despite of -r flag
Hi I'm launching ktunnel with my custom
bat
which creates non-privileged deployment/svc for ktunnel proxy server and then startsktunnel.exe
with-r
Also ktunnel image is changed to point to my inner docker registry. Beside that the deployment/svc are identical to what ktunnel creates. Ktunnel server starts ok with that deployment/svc.Something like so:
For some reason I see the second deployment version. It creates a pod that is stuck in tryin to download ktunnel image using its original url. And
oc wait
waits for this second pod until timeout. So even before ktunnel.exe itself is called. Why does this happen? Does ktunnel server create it? And how do I prevent that?