-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
headless svc forwarding behaviour changed for sts with single pod #133
Labels
bug
Something isn't working
Comments
This is a bug introduced in 1.14. The last few contributions have caused some issues I need to unwind. I am scheduling some time to work on this in the next two weeks. Thank you for raising this issue. |
cjimti
added a commit
that referenced
this issue
Jul 7, 2020
FIX: fix a bug for issue #133 (when sts scale to replicas 1)
Fixed in 1.17.2 |
D3-LucaPiombino
pushed a commit
to CodeCoil/kubefwd
that referenced
this issue
Jun 13, 2024
FIX: fix a bug for issue txn2#133 (when sts scale to replicas 1)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We noticed that kubefwd 14.x behaves differently for forwarding headless services forwarding to a single sts container
kubefwd 1.13.1
kubefwd 14.2
If the kafka-sts is scaled to 2 with 14.2, it will result in:
in 14.2, this is probably caused because of this check https://github.com/txn2/kubefwd/blob/1.14.2/cmd/kubefwd/services/services.go#L431
and this statement: https://github.com/txn2/kubefwd/blob/1.14.2/cmd/kubefwd/services/services.go#L458
Our apps are configured to use
kafka-sts-0.kafka-headless-svc:9092
and therefore fail with 14.2.We should be able to fix it while using
kafka-headless-svc:9092
instead but we are wondering if this is the new way to go or an issue?The text was updated successfully, but these errors were encountered: