-
Notifications
You must be signed in to change notification settings - Fork 158
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
chore: renames IngressGatewaySpec type to GatewaySpec #1144
chore: renames IngressGatewaySpec type to GatewaySpec #1144
Conversation
@@ -246,7 +246,7 @@ spec: | |||
certificate: | |||
description: Certificate specifies configuration of | |||
the TLS certificate securing communications of the | |||
for Ingress Gateway. | |||
for gateway. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should not be a change in bundle/manifests ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The godoc changed because the type itself is not really about "ingress". It is Istio Gateway resource which can applied on ingress or egress service. Let me review it more thoroughly though. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that Check config and readme updates / Ensure generated files are included (pull_request)
job is not commenting on the PR (anymore?)
/cc @AjayJagan
3d3e6c9
to
7cfbae0
Compare
Original name is confusing as it does not actually define anything related to the ingress. It is configuring Istio Gateway resource which is, in case of Model Serving, attached to ingress service. This change makes the change of the golang type, but not publicly exposed `ingressGateway` config defined for KServe component.
7cfbae0
to
f943ac5
Compare
Putting on hold to prevent auto-merge. I would like @israel-hdez to weigh in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine to me. Certainly, the type is applicable to either Ingress or Egress gateways.
In the exposed API, though, I think the ingress
on the name do is relevant.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: israel-hdez, zdtsw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e80dcbe
into
opendatahub-io:incubation
…ervices#1144) Original name is confusing as it does not actually define anything related to the ingress. It is configuring Istio Gateway resource which is, in case of Model Serving, attached to ingress service. This change makes the change of the golang type, but not publicly exposed `ingressGateway` config defined for KServe component.
…ervices#1144) Original name is confusing as it does not actually define anything related to the ingress. It is configuring Istio Gateway resource which is, in case of Model Serving, attached to ingress service. This change makes the change of the golang type, but not publicly exposed `ingressGateway` config defined for KServe component. (cherry picked from commit e80dcbe)
Original name is confusing as it does not actually define anything related to the ingress. It is configuring Istio Gateway resource which is, in case of Model Serving, attached to ingress service. This change makes the change of the golang type, but not publicly exposed `ingressGateway` config defined for KServe component. (cherry picked from commit e80dcbe)
Description
The original name is confusing as it does not define anything related to the ingress. It configures Istio Gateway resource which is attached to ingress service in case of Model Serving.
Important
This change makes the change of the Golang type only. It does not change publicly exposed
ingressGateway
config defined for KServe component underDataScienceCluster
.How Has This Been Tested?
Screenshot or short clip
Merge criteria