You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposed Solution
The solution is quite easy, change the servicePort to be the same name as the targetPort. For both SolrCloud and SolrPrometheusExporter Services.
This should not interrupt any traffic for solrClouds, as the Ingress rules use port numbers instead of port names.
The text was updated successfully, but these errors were encountered:
Describe the bug
There is a bug with certain providers of Kube, where network requests fail if a Service's port name and targetPort name do not equal.
More information can be found here: GoogleCloudPlatform/k8s-multicluster-ingress#196
Proposed Solution
The solution is quite easy, change the servicePort to be the same name as the targetPort. For both SolrCloud and SolrPrometheusExporter Services.
This should not interrupt any traffic for solrClouds, as the Ingress rules use port numbers instead of port names.
The text was updated successfully, but these errors were encountered: