-
Notifications
You must be signed in to change notification settings - Fork 690
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
internal/dag: move ListenerName to Listener struct #4149
Conversation
Moves the ListenerName field from VirtualHost to Listener, to better reflect the data model. This field is now populated by the listener processor. Signed-off-by: Steve Kriss <krisss@vmware.com>
const ( | ||
HTTP_LISTENER_NAME = "ingress_http" | ||
HTTPS_LISTENER_NAME = "ingress_https" | ||
) |
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.
I wasn't quite sure if it made sense to have these + the constants currently defined in internal/xdscache/v3 be consolidated (meaning the DAG listener names always equal the Envoy listener names), so for now I left them separate. Open to input here.
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.
I think this is fine for now. As @stevesloka said in another comment, if we do multiple listeners, all of this is going to need to change anyway.
Codecov Report
@@ Coverage Diff @@
## main #4149 +/- ##
=======================================
Coverage 72.55% 72.56%
=======================================
Files 115 115
Lines 10032 10032
=======================================
+ Hits 7279 7280 +1
+ Misses 2598 2597 -1
Partials 155 155
|
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.
Looking ahead, when you add additional listeners, we need a way to give them new names.
There might be "http_new" listeners, "ingress_tcp", "ingress_udp" etc. Today there's room for that in a Gateway.Spec.Name.
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 LGTM, I think it gives us a place to build from for multiple listeners later.
const ( | ||
HTTP_LISTENER_NAME = "ingress_http" | ||
HTTPS_LISTENER_NAME = "ingress_https" | ||
) |
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.
I think this is fine for now. As @stevesloka said in another comment, if we do multiple listeners, all of this is going to need to change anyway.
Moves the ListenerName field from VirtualHost
to Listener, to better reflect the data model.
This field is now populated by the listener
processor.
Signed-off-by: Steve Kriss krisss@vmware.com