Enable Webhook Warning messages, add Gateway API integration and simply Ingress integration #643
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new field under
.spec.router
for NIMService and NeMo Microservices, for integrating with Ingress or Gateway API.The created routing object will have the hostname in the format
<.metadata.name>.<.spec.router.hostDomainName>
Gateway API
Sample
router
for Gateway API integrationOnly HTTPRoutes is supported from Gateway API.
GRPCRoutes is pending.
Ingress
Sample
router
for Ingress integrationDeprecation
NIMService.spec.expose.ingress
will be deprecated. The field is present, it will not be used to create Ingress objects, and a warning message from webhook will be display.The deprecated fields will remain for sometimes for backward compatibility.