-
Notifications
You must be signed in to change notification settings - Fork 71
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
[Enhancement] add appProtocol in fe service #288
[Enhancement] add appProtocol in fe service #288
Conversation
5e2e041
to
5dbcbbb
Compare
Name: sp.Name, | ||
Port: sp.Port, | ||
NodePort: sp.NodePort, | ||
Protocol: corev1.ProtocolTCP, | ||
TargetPort: intstr.FromInt(int(sp.ContainerPort)), | ||
}) | ||
} | ||
if servicePort.Name == FeQueryPortName { |
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.
how about the webPort? does it need to add appProtocol http
?
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.
Do not need. Istio can detect http protocol. See https://istio.io/latest/docs/ops/deployment/requirements/#server-first-protocols
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.
didn't see our webport related to the server-first-protocol document. HTTP protocol doesn't look like a server-first-protocol per the description in the doc.
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.
MySQL is a server-first-protocol, so we only need to add appProtocol to the query port, 9030.
ci operator failure, might need take a look @yandongxiao |
…arrocks on Istio service mesh Signed-off-by: yandongxiao <[email protected]>
5dbcbbb
to
3241e47
Compare
Fixes: #287