2

Before I begin, I would like to mention that I am on the free trial version of GKE. I have a simple server running in a GKE cluster. I have a service that I use to expose the server. I am trying to configure an Ingress Controller and attach it to this service.

Everything works perfectly if my service is of type LoadBalancer, NodePort. However, if my service is of type ClusterIP, I get an error saying 

error while evaluating the ingress spec: service "default/simple-server" is type "ClusterIP"
, expected "NodePort" or "LoadBalancer"

GKE then stops trying to provision an IP for the ingress. Why can't I provision a service of type clusterIP and is there a work around?

I tried using annotations.kubernetes.io/ingress.class: "nginx" and it still didn't work.

goldentiger
  • 67
  • 2
  • 8
  • I mean the whole idea of having an Ingress controller is to filter access to my server. If I have to start the service as loadbalancer/nodeport, I am basically opening a direct unprotected gateway to my k8 cluster. – goldentiger Oct 10 '19 at 01:38

3 Answers3

2

The native GKE ingress controller does not support ClusterIP, but it works perfectly with LoadBalancer and NodePort type. Take a look at this issue

Non-native ingress controller Nginx works with ClusterIP.

Kamol Hasan
  • 12,218
  • 1
  • 37
  • 46
2

That's normal and it's pretty simple why you have the error.

A ClusterIP service is an internal only service inside of your Kubernetes cluster and what you are trying to create (from what I undestood) is a publicly exposed service using ingress, meaning you are going to create a Google Load balancer.

Now the why it doesn't support ClusterIP is because when you create the ingress, the LB resource created inside google cloud needs a target port on your cluster to call on And for that you need to expose an ip/port for it.

I would not recommend combining LB service (wich by default create a LB on cloud provider) and ingress, but stay on a nodeport/ingress duo that is cleaner.

Bonus: The annotation you used is for internal services with ingress to be linked to your ingress controller. This will allow the ingress-controller to list the hosts and proxy traffic to the right service.

night-gold
  • 2,202
  • 2
  • 20
  • 31
0

You can use Ingress to access a ClusterIP in GKE by setting the annotation cloud.google.com/neg: '{"ingress": true}' to the service.

apiVersion: v1
kind: Service
metadata:
  name: myapp
  annotations:
    cloud.google.com/neg: '{"ingress": true}'
...

See also answer https://stackoverflow.com/a/68271142 in the related question Why does Google Cloud show an error when using ClusterIP

user2355282
  • 727
  • 8
  • 9