You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to #1021, auto port forwarding no longer works for recent versions/variants of k8s (1.22+) as the iptable rules churn. I tried to use
portForwards:
- guestPort: <someNodePort>
...
which doesn't appear to work. An interesting workaround that does work is that to run nc -l -p <someNodePort> in the guest and port forwarding to <someNodePort> would work. As soon as I terminate the nc process, port forwarding stops working. Note, the nc hack doesn't require portForwards to be declared in the lima yaml.
Any ideas to make portForwards to work as expected without the kludgy nc -l workaround?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Due to #1021, auto port forwarding no longer works for recent versions/variants of k8s (1.22+) as the iptable rules churn. I tried to use
which doesn't appear to work. An interesting workaround that does work is that to run
nc -l -p <someNodePort>
in the guest and port forwarding to<someNodePort>
would work. As soon as I terminate thenc
process, port forwarding stops working. Note, the nc hack doesn't require portForwards to be declared in the lima yaml.Any ideas to make
portForwards
to work as expected without the kludgync -l
workaround?Beta Was this translation helpful? Give feedback.
All reactions