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
When i see inside pod it showing empty in server host
[opensearch-dashboards@kibana-opensearch-dashboards-676b8d69c4-tbn55 ~]$ env | grep SERVER
SERVER_HOST=
We are using in our values.yaml file like below.
serverHost: "eth0:ipv6"
serverHost: "global:ipv6"
serverHost: "[::0]"
service:
type: ClusterIP
ipFamilies:
IPv6
Still we were unable to deploy the opensearch-dashboard pod.
Please tell us how to overcome this issue.
Thanks,
Anil
The text was updated successfully, but these errors were encountered:
[Untriage]
Hey @ganilmca happy to help but this looks to me more like an error from kubernetes end and not with OpenSearch helm chart? Did you setup work with regular ipv4? Also did you set use server.host to set the ipv6?
Adding @kavilla@AMoo-Miki is there a limitation setting server.host with an ipv6 from OpenSearch Dashboards?
Hi Team,
We were unable to do port-forward in opensearch-dashboard pod in kubernates cluster by using ipv6 address like below command.
kubectl port-forward opensearch-dashboards-57b46c69ff-q25pw 5601:5601 --address [2a00:fbc:3110:1502:b520:22:1:0] -n ns
And also unable to run curl command like below.
curl -gkv -u admin:admin http://[2a00:fbc:3110:1502:c01e:b55:c9f1:5101]:5601
curl: (7) Failed connect to 2a00:fbc:3110:1502:c01e:b55:c9f1:5101:5601; Connection refused
We were getting "Connection refused" here.
When i see inside pod it showing empty in server host
[opensearch-dashboards@kibana-opensearch-dashboards-676b8d69c4-tbn55 ~]$ env | grep SERVER
SERVER_HOST=
We are using in our values.yaml file like below.
serverHost: "eth0:ipv6"
serverHost: "global:ipv6"
serverHost: "[::0]"
service:
type: ClusterIP
ipFamilies:
Still we were unable to deploy the opensearch-dashboard pod.
Please tell us how to overcome this issue.
Thanks,
Anil
The text was updated successfully, but these errors were encountered: