IPVS mode: traffic sent from pods to an external LoadBalancer IP is NOT directed to the respective cluster IP instead

kubernetes / kube-proxy

kube-proxy component configs

Apache License 2.0

183 stars 90 forks source link

IPVS mode: traffic sent from pods to an external LoadBalancer IP is NOT directed to the respective cluster IP instead #18

Closed amorozkin closed 1 year ago

amorozkin commented 1 year ago

But, if I'm not mistaken, according to docs it do should to.

kube-proxy:v1.23.4

amorozkin commented 1 year ago

As I'm not sure picking the tight repo for the issue - here is the duplicate I've just posted to main repo - https://github.com/kubernetes/kubernetes/issues/115931

sftim commented 1 year ago

Let's close this. If it turns out that this is the right repo, we can get Prow to move https://github.com/kubernetes/kubernetes/issues/115931 into this repo.

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

danwinship commented 1 year ago

As I'm not sure picking the tight repo for the issue - here is the duplicate I've just posted to main repo - kubernetes/kubernetes#115931

yeah, k/k is the right repo

danwinship commented 1 year ago

/close

k8s-ci-robot commented 1 year ago

@danwinship: Closing this issue.

In response to [this](https://github.com/kubernetes/kube-proxy/issues/18#issuecomment-1658327358): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.