Skip to content

fix: Correct the setup of the KGateway Envoy service to be a proper NodePort service #57

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

Merged
merged 5 commits into from
Apr 24, 2025

Conversation

shmuelk
Copy link
Collaborator

@shmuelk shmuelk commented Apr 24, 2025

This PR corrects setup of the KGateway Envoy's service to be a proper NodePort service.

To do this:

  1. The created service was renamed to that which is used by KGateway's Controller for the Envoy pod
  2. A KGateway GatewayParameters object was added to set the Service type to NodePort. Unfortunately, this
    by itself is not enough, as one can't set the nodePort that the service will be mapped to.

@shmuelk shmuelk requested review from elevran and shaneutt April 24, 2025 11:37
labels:
gateway.istio.io/managed: istio.io-gateway-controller
app.kubernetes.io/instance: inference-gateway
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are these needed, filled in automatically by RHOS?
If not needed, it may be better to remove so we keep files to their minimum and it is clear what's needed. Otherwise people continue copying in fear of breaking.

@shmuelk shmuelk merged commit 8c81c0c into neuralmagic:dev Apr 24, 2025
2 checks passed
@shmuelk shmuelk deleted the kind-kgw-nodeport branch April 24, 2025 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants