How to expose "demo" ECK elastic/kibana services on Kubernetes? loadbalancer?

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hi,
I've following the quickstart demo (Quickstart | Elastic Cloud on Kubernetes [2.5] | Elastic) and have an ES I can port-forward to,but I want to be able to access my ES instance using e.g. a loadbalancer. Usually, I'd add a service to expose my deployment but that doesn't appear to work and feels like I'm working around the idea of using an operator. Please can someone tell me how to expose my new ES. Thanks,

	kubectl get services
	NAME                          TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
	kubernetes                    ClusterIP      10.152.183.1     <none>        443/TCP        213d
	quickstart-es-transport       ClusterIP      None             <none>        9300/TCP       5h39m
	quickstart-es-http            ClusterIP      10.152.183.141   <none>        9200/TCP       5h39m
	quickstart-es-internal-http   ClusterIP      10.152.183.68    <none>        9200/TCP       5h39m
	quickstart-es-default         ClusterIP      None             <none>        9200/TCP       5h39m
	quickstart-kb-http            ClusterIP      10.152.183.187   <none>        5601/TCP       5h25m
	coffee-service                LoadBalancer   10.152.183.144   <pending>     80:30628/TCP   3h12m
	
	
	
	kubectl describe service quickstart-kb-http
	Name:              quickstart-kb-http
	Namespace:         default
	Labels:            common.k8s.elastic.co/type=kibana
					   kibana.k8s.elastic.co/name=quickstart
	Annotations:       <none>
	Selector:          common.k8s.elastic.co/type=kibana,kibana.k8s.elastic.co/name=quickstart
	Type:              ClusterIP
	IP Family Policy:  SingleStack
	IP Families:       IPv4
	IP:                10.152.183.187
	IPs:               10.152.183.187
	Port:              https  5601/TCP
	TargetPort:        5601/TCP
	Endpoints:         10.1.6.194:5601
	Session Affinity:  None
	Events:            <none>
1 Like
2

I'm going with the following Ingress:

	apiVersion: networking.k8s.io/v1
	kind: Ingress   #https://kubernetes.io/docs/concepts/services-networking/ingress/
	metadata:
	  name: http-ingress
	  # annotations:
	  #   nginx.ingress.kubernetes.io/rewrite-target: /
	spec:
	  #ingressClassName: http-ingress
	  rules:
	  - http:
		  paths:
		  - path: /
			pathType: Prefix
			backend:
			  service:
				name: quickstart-es-http
				port:
				  number: 9200
3

I'm having a similar issue. But one step earlier, I can't get the port-forwarding to work. Maybe using the loadbalancer would help that too.

I did find the advice to add the following to the env variables on the container:
env:

  • name: "NETWORK_HOST"
    value: "site,lo"

But the quickstart ymls don't have container specifications, so I think we have to add that first.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.