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 2021/12/02 09:16:29 UTC
[GitHub] [solr-operator] gthvidsten opened a new issue #381: Accessing Solr without using an Ingress
gthvidsten opened a new issue #381:
URL: https://github.com/apache/solr-operator/issues/381
The Solr Operator tutorial wants to use an Ingress so that Solr is available from outside Kubernetes. However, I don't want it to be available outside Kubernetes, only use it internally. Normally with a deployment you would create a Service that other pods connect to, but I can't see any services being installed using Helm.
How can other pods in the same cluster access Solr without having to make Solr available through an Ingress?
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984666776
Thanks for the swift reply :)
I tried doing a `kubectl port-forward` to my "example-solrcloud-common" (8080 -> 80), but when I access http://localhost:8080 I get the following error in the shell:
```
Handling connection for 8080
E1202 15:12:11.516200 32672 portforward.go:400] an error occurred forwarding 8080 -> 8983:
error forwarding port 8983 to pod 8a8abe2427d899d7e84f2e524fc43747d9e05ba49d23eda7bf263f731e66d6fa, uid :
failed to execute portforward in network namespace "/var/run/netns/cni-8c979efc-93e7-93a6-a2fb-a78a8185e794":
failed to dial 8983: dial tcp4 127.0.0.1:8983: connect: connection refused
```
EDIT:
On second thought, that might be because my solr containers aren't starting. It seems there's a problem pulling a specific image: `library/busybox:1.28.0-glibc`
This is not an image that is present in our Container Registry, nor does that name include a FQDN in the image name... so I guess the problem is the Helm Chart setting up a Pod to require this image, but it is non-existing in our environment?
It seems there's a similar problem for the Zookeeper Pods, but for a different image: `pravega/zookeeper:0.2.13`
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985742900
I'm getting `ErrImagePull` with `docker.io` as well.
I've been experimenting with these addresses as the Azure Kuberenets Service we're running on doesn't seem to want to pull directly from Docker, so I need to prefix all images with Docker's FQDN, which is not really documented anywhere.
`index.docker.io` and `docker.io` seems to work for the Solr images, but it just refuses to get the Zookeeper image.
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985742900
I'm getting `ErrImagePull` with `docker.io` as well.
I've been experimenting with these addresses as the Azure Kuberenets Service we're running on doesn't seem to want to pull directly from Docker, so I need to prefix all images with Docker's FQDN, which is not really documented anywhere.
`index.docker.io` and `docker.io` seems to work for the Solr images, but it just refuses to get the Zookeeper image.
EDIT:
It does not seem to be a rate limitation or authorization issue. The error just says "ErrImagePull" without any additional information suggesting error scenarios.
EDIT2:
I can see now from the events in one of the pods that it is assigned to our Windows node, and not our Linux node. I guess that's a big part of the problem here.
I did add this to the top of the `values.yaml` file, but maybe that's not enough?
```
nodeSelector:
kubernetes.io/os: linux
```
Another odd thing is that I did see a message about not being able to find a compatible Windows/amd64 image a couple of times, but after adding the above to `values.yaml` I never saw them again so I figured it worked... but maybe not enough.
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985742900
I'm getting `ErrImagePull` with `docker.io` as well.
I've been experimenting with these addresses as the Azure Kuberenets Service we're running on doesn't seem to want to pull directly from Docker, so I need to prefix all images with Docker's FQDN, which is not really documented anywhere.
`index.docker.io` and `docker.io` seems to work for the Solr images, but it just refuses to get the Zookeeper image.
EDIT:
It does not seem to be a rate limitation or authorization issue. The error just says "ErrImagePull" without any additional information suggesting error scenarios.
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984758706
How can I do this in the `helm install` command?
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-989140354
Closing this as we're way past the original question. Creating a new issue for the nodeSelector issues
--
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] gthvidsten closed issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten closed issue #381:
URL: https://github.com/apache/solr-operator/issues/381
--
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] janhoy commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
janhoy commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984604208
You only need the ingress for external traffic. Applications running inside the cluster can use the service name for your cluster. Say you have a SolrCloud deployment called "example" with 2 pods, you will see that there is a `-common` service created that will load balance between the two pods, and you can also access each node with the `-0` and `-1` service names.
```
NAME READY STATUS RESTARTS
pod/example-solrcloud-0 1/1 Running 0
pod/example-solrcloud-1 1/1 Running 0
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
service/example-solrcloud-common ClusterIP 10.43.185.20 <none> 80/TCP
service/example-solrcloud-0 ClusterIP 10.43.69.190 <none> 80/TCP
service/example-solrcloud-1 ClusterIP 10.43.16.234 <none> 80/TCP
```
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985705378
I don't know why that link works now. It gave a 404 earlier today. Might've been a glitch at Docker's end.
However, I changed the `tag` to be `0.2.12` but I still have problems.
The `example-solrcloud-zookeeper` pods wants to pull the image, based on this event:
`Pulling image "index.docker.io/pravega/zookeeper:0.2.12"`
But it is immediately followed by `Error: ErrImagePull`
Can you see any typos in the image name? Something is obviously wrong, but I'm at a loss to what.
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985376187
It seems there's a problem with the zookeeper image.
I've tried with `docker.io/library/zookeeper` and `index.docker.io/zookeeper` but it seems it can't find the `0.2.13` label... which is not really surprising as that label is not listed [here](https://index.docker.io/_/zookeeper).
I also found some references to `pravega/zookeeper` in the default `values.yaml` you gave a link to, but that seems to not exist any more.
What would be a correct zookeeper image repository?
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985376187
It seems there's a problem with the zookeeper image.
I've tried with `docker.io/library/zookeeper` and `index.docker.io/zookeeper` but it seems it can't find the `0.2.13` label... which is not really surprising as that label is not listed [here](https://index.docker.io/_/zookeeper).
I also found some references to `pravega/zookeeper` but that seems to not exist any more.
What would be a correct zookeeper image repository?
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984666776
Thanks for the swift reply :)
I tried doing a `kubectl port-forward` to my "example-solrcloud-common" (8080 -> 80), but when I access http://localhost:8080 I get the following error in the shell:
```
Handling connection for 8080
E1202 15:12:11.516200 32672 portforward.go:400] an error occurred forwarding 8080 -> 8983: error forwarding port 8983 to pod 8a8abe2427d899d7e84f2e524fc43747d9e05ba49d23eda7bf263f731e66d6fa, uid : failed to execute portforward in network namespace "/var/run/netns/cni-8c979efc-93e7-93a6-a2fb-a78a8185e794": failed to dial 8983: dial tcp4 127.0.0.1:8983: connect: connection refused
```
EDIT:
On second thought, that might be because my solr containers aren't starting. It seems there's a problem pulling a specific image: `library/busybox:1.28.0-glibc`
This is not an image that is present in our Container Registry, nor does that name include a FQDN in the image name... so I guess the problem is the Helm Chart setting up a Pod to require this image, but it is non-existing in our environment?
--
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 #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984764709
You can either pass save these values as a file and pass it as an override values.yaml through `--values <file_name>`, which will use the default values provided in the helm chart, expect for the overrides you have provided in your file.
If you don't want to manage files, then you can just use `--set` for all of the above things you want to change.
```
helm install example-solr apache-solr/solr --version 0.5.0 \
--set image.repository="custom.docker.repo/solr" \
--set image.tag=8.4 \
--set dataStorage.persistent.pvc.storageClassName="solr-storage" \
--set zk.provided.persistence.spec.storageClassName="solr-storage"
--set zk.provided.image.repository="custom.docker.repo/zookeeper" \
--set busyBoxImage.repository="custom.docker.repo/busybox" \
--set busyBoxImage.tag="1.30.0"
```
Passing each value independently through `--set`. You can find more information in the [helm docs](https://helm.sh/docs/helm/helm_install/).
--
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] gthvidsten edited a comment on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten edited a comment on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984666776
Thanks for the swift reply :)
I tried doing a `kubectl port-forward` to my "example-solrcloud-common" (8080 -> 80), but when I access http://localhost:8080 I get the following error in the shell:
```
Handling connection for 8080
E1202 15:12:11.516200 32672 portforward.go:400] an error occurred forwarding 8080 -> 8983:
error forwarding port 8983 to pod 8a8abe2427d899d7e84f2e524fc43747d9e05ba49d23eda7bf263f731e66d6fa, uid :
failed to execute portforward in network namespace "/var/run/netns/cni-8c979efc-93e7-93a6-a2fb-a78a8185e794":
failed to dial 8983: dial tcp4 127.0.0.1:8983: connect: connection refused
```
EDIT:
On second thought, that might be because my solr containers aren't starting. It seems there's a problem pulling a specific image: `library/busybox:1.28.0-glibc`
This is not an image that is present in our Container Registry, nor does that name include a FQDN in the image name... so I guess the problem is the Helm Chart setting up a Pod to require this image, but it is non-existing in our environment?
It seems there's a similar problem for the Zookeeper Pods, but for a different image: `pravega/zookeeper:0.2.13`
I installed using the following command:
```
helm install example-solr apache-solr/solr --version 0.5.0 \
--set image.tag=8.4 \
--set dataStorage.persistent.pvc.storageClassName="solr-storage" \
--set zk.provided.persistence.spec.storageClassName="solr-storage"
```
Where `solr-storage` is an existing (and functioning) Storage Class
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985376187
It seems there's a problem with the zookeeper image.
I've tried with `docker.io/library/zookeeper` and `index.docker.io/zookeeper` but it seems it can't find the `0.2.13` label... which is not really surprising as that label is not listed [here](https://index.docker.io/_/zookeeper).
I also found some references to `praveda/zookeeper` but that seems to not exist any more.
What would be a correct zookeeper image repository?
--
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 #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985710102
I'm unsure what `index.docker.io` is. maybe try `docker.io` instead?
Are you being rate limited by docker?
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984798732
Awesome! Thank you so much! :D
--
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 #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984786918
Ahh I think that is a sentence left over from before the Solr helm chart existed. The best example `values.yaml` file is actually the default: https://github.com/apache/solr-operator/blob/v0.5.0/helm/solr/values.yaml
You don't need to (and shouldn't) include everything, since helm will use the default `values.yaml` as the starting point, then replace anything that is in your override values.yaml. So you can take the default values.yaml and remove anything that you don't want to change. For the example you have provided, you can merely use the following: (sets solr to use 8.4, uses a custom storage class name, and persistent storage for solr, and uses custom repositories for every image)
```yaml
image:
repository: "custom.docker.repo/solr"
tag: "8.4"
dataStorage:
type: persistent
persistent:
pvc:
storageClassName: "solr-storage"
zk:
provided:
image:
repository: "custom.docker.repo/zookeeper"
persistence:
spec:
storageClassName: "solr-storage"
busyBoxImage:
repository: "custom.docker.repo/busybox"
```
--
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 #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984739720
You can override the image for that container with:
```yaml
busyBoxImage:
repository: "busybox"
tag: "1.28.0-glibc"
pullPolicy: ""
imagePullSecret: ""
```
This image is used for an init container that sets up the data directory/`solr.xml`.
And yes, the Solr Operator contains defaults that assume access to the default docker registry, docker hub. If you want to use a different repository then you need to set that for each image.
```yaml
image:
repository: "solr"
tag: ""
pullPolicy: ""
imagePullSecret: ""
zk:
provided:
image:
repository: "pravega/zookeeper"
tag: ""
pullPolicy: IfNotPresent
imagePullSecret: ""
busyBoxImage:
repository: "busybox"
tag: "1.28.0-glibc"
pullPolicy: ""
imagePullSecret: ""
```
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984666776
Thanks for the swift reply :)
I tried doing a `kubectl port-forward` to my "example-solrcloud-common" (8080 -> 80), but when I access http://localhost:8080 I get the following error in the shell:
```
Handling connection for 8080
E1202 15:12:11.516200 32672 portforward.go:400] an error occurred forwarding 8080 -> 8983: error forwarding port 8983 to pod 8a8abe2427d899d7e84f2e524fc43747d9e05ba49d23eda7bf263f731e66d6fa, uid : failed to execute portforward in network namespace "/var/run/netns/cni-8c979efc-93e7-93a6-a2fb-a78a8185e794": failed to dial 8983: dial tcp4 127.0.0.1:8983: connect: connection refused
```
--
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] gthvidsten commented on issue #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
gthvidsten commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984780794
Ah, values.yaml... I remember seeing something about that.
The quickstart tutorial in the documentation said "we will create a yaml" but then proceeds without any yaml, and there's no examples as far as I've been able to find.
Do you have an example values.yaml file available?
--
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 #381: Accessing Solr without using an Ingress
Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #381:
URL: https://github.com/apache/solr-operator/issues/381#issuecomment-985686718
https://hub.docker.com/r/pravega/zookeeper is the correct image, it does not use the official zookeeper image.
You should also be using the `0.2.12` image, not `0.2.13`. It should be using that by default, so it's surprising that it was trying to use the 0.2.13 label...
--
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