HoustonPutman commented on code in PR #576: URL: https://github.com/apache/solr-operator/pull/576#discussion_r1228126750
########## docs/solr-cloud/solr-cloud-crd.md: ########## @@ -151,6 +151,16 @@ If both of those criteria are met, then an individual ClusterIP Service will be If you are using an `Ingress` for external addressability, you can customize the created `Ingress` through `SolrCloud.spec.customSolrKubeOptions.ingressOptions`. Under this property, you can set custom `annotations`, `labels` and an `ingressClassName`. +**Note:** If you have no need for an `Ingress` or a specific hostname to address your SolrCloud cluster you can create a simple loadbalancer that can be addressed from outside the kubernetes cluster. To achieve this you can add annotations to `SolrCloud.spec.customSolrKubeOptions.headlessServiceOptions.annotations`. Snippet below shows you can create an NLB on AWS: + +```yaml +headlessServiceOptions: + annotations: + service.beta.kubernetes.io/aws-load-balancer-type: external + service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip + service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing Review Comment: oh interesting, I didn't realize that these annotations would add an IP per pod, I thought it would be one IP for the service. If it exposes individual Solr addresses, then that is certainly a good reason to use the headless service. -- 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
