You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by GitBox <gi...@apache.org> on 2022/01/25 13:24:42 UTC
[GitHub] [solr-operator] otienoanyango opened a new issue #400: LoadBalancer option for common service
otienoanyango opened a new issue #400:
URL: https://github.com/apache/solr-operator/issues/400
I have a setup on Google Kubernetes Engine where I deploy a cluster in each of three regions. To index data, I need access from outside the cluster, but all I need is an internal IP. I am using annotations that GKE provides for this but it requires being able to set `spec.Type: LoadBalancer` for the service.
```yaml
apiVersion: v1
kind: Service
metadata:
annotations:
cloud.google.com/neg: '{"ingress":true}'
networking.gke.io/internal-load-balancer-allow-global-access: "true"
networking.gke.io/load-balancer-type: Internal
spec:
type: LoadBalancer
...
```
is there a way to set the type for the commonService
--
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-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org
[GitHub] [solr-operator] HoustonPutman commented on issue #400: LoadBalancer option for common service
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #400:
URL: https://github.com/apache/solr-operator/issues/400#issuecomment-1039268498
There is no way to currently do this, but it is something that we could look into.
My first thought is that the common service is used by the operator to communicate with the Solr Cloud within the Kubernetes cluster, so if we instead make it a loadBalancer service, would the same internal DNS entry still exist?
--
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-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org
[GitHub] [solr-operator] HoustonPutman commented on issue #400: LoadBalancer option for common service
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #400:
URL: https://github.com/apache/solr-operator/issues/400#issuecomment-1039268498
There is no way to currently do this, but it is something that we could look into.
My first thought is that the common service is used by the operator to communicate with the Solr Cloud within the Kubernetes cluster, so if we instead make it a loadBalancer service, would the same internal DNS entry still exist?
--
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-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org