Ingress是否可以与ClusterIP服务一起使用?

本文介绍了Ingress是否可以与ClusterIP服务一起使用?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我已经设置了一些服务和入口以尝试SSL终止.使用LoadBalancer和NodePort服务作为后端根本没有问题，但是使用ClusterIP服务根本不起作用.

I've setup some services and ingresses to try out the SSL termination. I had no problem at all with LoadBalancer and NodePort services as backend but it's not working at all with ClusterIP service.

尽管Ingress的后端被描述为正常，但我收到的HTTP错误并非来自我的应用程序.

Although the Ingress' backend is described as healthy, I get an HTTP error that do not come from my application.

$ kubectl describe ing nginx-cluster-ssl-ingress Name: nginx-cluster-ssl-ingress Namespace: default Address: X.X.X.X Default backend: nginx-cluster-svc:80 (...) TLS: ssl-certificate terminates Rules: Host Path Backends ---- ---- -------- Annotations: https-target-proxy: k8s-tps-default-nginx-cluster-ssl-ingress static-ip: k8s-fw-default-nginx-cluster-ssl-ingress target-proxy: k8s-tp-default-nginx-cluster-ssl-ingress url-map: k8s-um-default-nginx-cluster-ssl-ingress backends: {"k8s-be-30825":"HEALTHY"} forwarding-rule: k8s-fw-default-nginx-cluster-ssl-ingress https-forwarding-rule: k8s-fws-default-nginx-cluster-ssl-ingress Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 28m 28m 1 {loadbalancer-controller } Normal ADD default/nginx-cluster-ssl-ingress 27m 27m 1 {loadbalancer-controller } Normal CREATE ip: X.X.X.X

HTTP错误如下:

$ curl X.X.X.X/ default backend - 404%

我的问题很简单:是否可以与ClusterIP服务一起使用?如果应该在文档中或多或少地编写该文档，我应该在哪里解决该问题?

My question is quite simple: is it supposed to work with ClusterIP services? If it is supposed to as more or less written in the documentation, where should I have a look to resolve that issue?

谢谢！

推荐答案

本机GKE Ingress控制器不会支持ClusterIP，只有NodePort可用.

The native GKE Ingress controller do not support ClusterIP, only NodePort is working.

nginx之类的非本机Ingress控制器可以与ClusterIP服务一起使用.

Non-native Ingress controllers such as the nginx one do work with ClusterIP services.