HoustonPutman commented on issue #528: URL: https://github.com/apache/solr-operator/issues/528#issuecomment-1456355594
So there are three possible solutions here. - You run your indexing code in Kubernetes as well, that way `http://core-solrcloud-0.core-solrcloud-headless.default:8983/solr` will be reachable from the client. - You make the clusterState store an address for your individual solr nodes that is accessible from outside the cluster: `SolrCloud.spec.solrAddressability.external.useExternalAddress`. More information is available here: https://apache.github.io/solr-operator/docs/solr-cloud/solr-cloud-crd.html#addressability - You can use the Http2SolrClient/HttpSolrClient and not use the CloudSolrClient. That way the SolrJ Client will not try to find node addresses from Zookeeper, and will just use the one address that you provide. To be clear, you are using an ingress to make at least one endpoint available outside of your EKS cluster, correct? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
