Hi folks, I am getting the following error when I am trying to deploy Weaviate with helm chats on our internal k8’s.
{"action":"startup","error":"create member list: Failed to get final advertise address: No private IP address found, and explicit IP not provided","level":"error","msg":"could not init cluster state","time":"2024-03-14T15:18:14Z"}
my custom value file here,
service:
name: weaviate
type: NodePort
ports:
- name: http
protocol: TCP
port: 8080
nodePort: 30101
anything I am missing here ?
and also I didn’t find ingress file in templates ? Do I have to define it manually ? (
Hi @phaneendra !
Welcome to our community
Regarding the helm deployment, if you want to expose Weaviate, you will need to define an ingress yourself.
Here we have some discussions on that:
opened 01:01PM - 25 Feb 23 UTC
Is there a way to add GKE ManagedCertificates to the Helm values?
On that error log, what is the version you are using? How many replicas you set?
for what node is that error from?
Thanks!
I am using server version - version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.15"
on on-premise k8’s.
replicas - 1
I used similar AWS EKS LoadBalancer and ingress config to deploy on on-premise. It’s still throwing same error.
EKS custom values
service:
ports:
- name: http
protocol: TCP
port: 8080
ingress:
enabled: true
name: weaviate
port: 8080
On-premise custom values
service:
ports:
- name: http
protocol: TCP
port: 8080
ingress:
enabled: true
name: weaviate
host: <host-name>
port: 8080
className: nginx
annotations:
- nginx.ingress.kubernetes.io/scheme: internet-facing
- nginx.ingress.kubernetes.io/target-type: ip
- nginx.ingress.kubernetes.io/healthcheck-path: /v1/.well-known/ready
- nginx.ingress.kubernetes.io/healthcheck-port: '8080'
As my understanding, weaviate service on on-prem is unable to communicate to the pod. Endpoint is None.
weaviate
weaviate-headless <ip>:7000
on EKS
NAME ENDPOINTS
weaviate <ip>:8080
weaviate-headless <ip>:7000