Mixed linux and windows clusters

[chandlerkent]

First, thank you very much for ktunnel! We discovered it this week and are replacing our hacky usage of ngrok with this.

We have a mixed linux and windows node Kubernetes cluster and often the deploy of ktunnel fails if Kubernetes schedules it on a windows node. We can fix this by adding a nodeSelector manually to the deployment after ktunnel initiates it:

      nodeSelector:
        kubernetes.io/os: linux

This selector is specific to the labels we apply to our Kubernetes nodes (I think), so I don't believe ktunnel should adopt this, but I was wondering if there's a way we can add the nodeSelector to the deployment so it does not error?

If you can think of how you would like this feature added to ktunnel, I would be happy to contribute a PR as well.

[omrikiei]

Hi @chandlerkent, firstly thank you for the kind words! this really means a lot to me! Since the docker image pulled and used as the server is built for linux it's probably the reason it's failing. The easier way would be to use -r when running ktunnel, in this case the server side does not teardown on exit and can be reused. I'll also look into ways of customizing the injected/exported pieces using feature flags, will get back to you in this soon, promise!

[omrikiei]

Hey @chandlerkent - v1.4.4 supports adding node selector tags with the -q flag to the expose command:

-q, --node-selector-tags strings    tag and value seperated by the '=' character (i.e kubernetes.io/os=linux)

please let me know if it does the job

[chandlerkent]

That looks great! I will give it a try on Monday and let you know.

Thanks again!

[chandlerkent]

@omrikiei I can confirm this is working great for us. Thanks again!

[doctorpangloss]

this should be the default