search

knight42 / krelay

A better alternative to `kubectl port-forward` that can forward TCP or UDP traffic to IP/Host which is accessible inside the cluster.
MIT License
244 stars 14 forks source link

Add TopologySpreadConstraints to server pod #27

Closed ilpianista closed 6 months ago

ilpianista commented 6 months ago

Partially related to issue #24, we've exhausted the IPs in a single EC2 instance because all krelay servers where deployed to the same k8s node. We already setup a "krelay killer", but this could happen again if devs starts krelay servers without killing them in a short interval. Maybe a topologySpreadConstraints would make this problem a rare occurrence?

ilpianista commented 6 months ago

BTW would it help if krelay can reuse a single server pod?

Yes. Honestly I'm quite surprised it doesn't already. What's blocking that? :thinking:

knight42 commented 6 months ago

BTW would it help if krelay can reuse a single server pod?

Yes. Honestly I'm quite surprised it doesn't already. What's blocking that? 🤔

Well it used to, but some users want to cleanup the server pod afterwards, so I change the default behavior. It seems both behaviors are desired, we'd better leave the choice to users.

knight42 commented 6 months ago

@ilpianista Hi, krelay v0.0.7 has been released, please feel free to give it a try.