Skip to content
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

Scaling integration pod and the replicas are not able to receive traffic via UDP port #2847

Closed
haifzhan opened this issue Jan 4, 2022 · 2 comments

Comments

@haifzhan
Copy link

haifzhan commented Jan 4, 2022

Hi Apache Camel team:

Situation:

  1. I have an integration pod is listening on UDP 8444 and forward it to 30006, and it is configured in my-integration-service.yaml
  2. I am trying to scale the integration followed the document CAMEL K INTEGRATION SCALING

For instance I have 2 pods running after scale and only the first pod is capable of receiving incoming events.

I see a similar question under Issues scaling out camel-k integrations are not working correctly #1806. The service was enabled as a node port. As far as I know, the service trait only works for TCP not UDP.

Please help.

my-integration-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: my-integration
spec:
  type: NodePort
  selector:
    camel.apache.org/integration: my-integration
  ports:
    - protocol: UDP
      port: 8444
      targetPort: 8444
      nodePort: 30006
@haifzhan haifzhan changed the title Scaling integration pod, the replicas are not able to receive traffic Scaling integration pod and the replicas are not able to receive traffic via UDP port Jan 4, 2022
@haifzhan
Copy link
Author

haifzhan commented Jan 5, 2022

Some updates:
I killed the pod which is capable of receiving events when there's traffic and observed that the replica start receiving events. Now it turns out the settings are working properly.

What am I supposed to modify to make the traffic policy round robin?

@github-actions
Copy link
Contributor

github-actions bot commented Apr 6, 2022

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant