当负载平衡器获得随机端口时，Kubernetes nginx入口控制器

Question

我试图通过一个单一的主裸金属集群的入口公开地曝光kubernetes仪表盘。问题是，我使用的LoadBalancer (nginx控制器)服务没有打开我希望它打开/使用的80/443端口。相反，它从30-32k范围内获取一些随机端口。我知道我可以用--service-node-port-range来设置这个范围，但我非常肯定，一年前我不必在另一台服务器上这样做。我是不是漏掉了什么？

目前，这是我的堆栈/安装程序( Ubuntu 16.04的干净安装)：

• Nginx大会控制器(通过舵机安装)
• MetalLB
• 库伯奈特斯仪表盘
• Kubernetes仪表板入侵将在<domain>上公开部署
• 证书-经理(通过舵机安装)

k8s-dashboard-ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    # add an annotation indicating the issuer to use.
    cert-manager.io/cluster-issuer: letsencrypt-staging
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/secure-backends: "true"
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  name: kubernetes-dashboard-ingress
  namespace: kubernetes-dashboard
spec:
  rules:
  - host: <domain>
    http:
      paths:
      - backend:
          serviceName: kubernetes-dashboard
          servicePort: 443
        path: /
  tls:
  - hosts:
    - <domain>
    secretName: kubernetes-dashboard-staging-cert

这就是我的kubectl get svc -A的样子：

NAMESPACE              NAME                            TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)                      AGE
cert-manager           cert-manager                    ClusterIP      10.101.142.87    <none>          9402/TCP                     23h
cert-manager           cert-manager-webhook            ClusterIP      10.104.104.232   <none>          443/TCP                      23h
default                kubernetes                      ClusterIP      10.96.0.1        <none>          443/TCP                      6d6h
ingress-nginx          nginx-ingress-controller        LoadBalancer   10.100.64.210    10.65.106.240   80:31122/TCP,443:32697/TCP   16m
ingress-nginx          nginx-ingress-default-backend   ClusterIP      10.111.73.136    <none>          80/TCP                       16m
kube-system            kube-dns                        ClusterIP      10.96.0.10       <none>          53/UDP,53/TCP,9153/TCP       6d6h
kubernetes-dashboard   cm-acme-http-solver-kw8zn       NodePort       10.107.15.18     <none>          8089:30074/TCP               140m
kubernetes-dashboard   dashboard-metrics-scraper       ClusterIP      10.96.228.215    <none>          8000/TCP                     5d18h
kubernetes-dashboard   kubernetes-dashboard            ClusterIP      10.99.250.49     <none>          443/TCP                      4d6h

下面是关于正在发生的事情的更多示例：

1. curl -D- http://<public_ip>:31122 -H 'Host: <domain>'

- returns 308, as the protocol is http not https. This is expected

​

1. curl -D- http://<public_ip> -H 'Host: <domain>'

- `curl: (7) Failed to connect to <public_ip> port 80: Connection refused`
- port 80 is closed

​

1. curl -D- --insecure https://10.65.106.240 -H "Host: <domain>"

- reaching the dashboard through an internal IP obviously works and I get the correct k8s-dashboard html. 
- `--insecure` is due to the let's encrypt not working yet as the acme challenge on port 80 is unreachable.

​

因此，简单地说，我如何使2.工作？例如通过80/443达到服务？

编辑: Nginx入侵控制器.yaml

apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2020-02-12T20:20:45Z"
  labels:
    app: nginx-ingress
    chart: nginx-ingress-1.30.1
    component: controller
    heritage: Helm
    release: nginx-ingress
  name: nginx-ingress-controller
  namespace: ingress-nginx
  resourceVersion: "1785264"
  selfLink: /api/v1/namespaces/ingress-nginx/services/nginx-ingress-controller
  uid: b3ce0ff2-ad3e-46f7-bb02-4dc45c1e3a62
spec:
  clusterIP: 10.100.64.210
  externalTrafficPolicy: Cluster
  ports:
  - name: http
    nodePort: 31122
    port: 80
    protocol: TCP
    targetPort: http
  - name: https
    nodePort: 32697
    port: 443
    protocol: TCP
    targetPort: https
  selector:
    app: nginx-ingress
    component: controller
    release: nginx-ingress
  sessionAffinity: None
  type: LoadBalancer
status:
  loadBalancer:
    ingress:
    - ip: 10.65.106.240

编辑2: metallb configmap yaml

kind: ConfigMap
metadata:
  namespace: metallb-system
  name: config
data:
  config: |
    address-pools:
    - name: default
      protocol: layer2
      addresses:
      -  10.65.106.240-10.65.106.250

Answer 1

因此，为了解决第二个问题，正如我所建议的，您可以使用hostNetwork: true参数将容器端口映射到正在运行的主机。请注意，这不是推荐的做法，除非您有理由，否则您应该始终避免这样做。

示例：

apiVersion: v1
kind: Pod
metadata:
  name: nginx
  labels:
    app: nginx
spec:
  hostNetwork: true
  containers:
  - name: nginx
    image: nginx
    ports:
    - containerPort: 80
      hostPort: 80           # this parameter is optional, but recommended when using host network
      name: nginx

当我部署这个yaml时，我可以检查吊舱在哪里运行，并卷起主机的端口80。

root@v1-16-master:~# kubectl get po -owide
NAME                     READY   STATUS    RESTARTS   AGE     IP                NODE             NOMINATED NODE   READINESS GATES
nginx                    1/1     Running   0          105s    10.132.0.50       v1-16-worker-2   <none>           <none>

注意:现在我知道吊舱是在工作节点2上运行的，我只需要它的IP地址。

root@v1-16-master:~# kubectl get no -owide
NAME             STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION    CONTAINER-RUNTIME
v1-16-master     Ready    master   52d   v1.16.4   10.132.0.48   xxxx        Ubuntu 16.04.6 LTS   4.15.0-1052-gcp   docker://19.3.5
v1-16-worker-1   Ready    <none>   52d   v1.16.4   10.132.0.49   xxxx        Ubuntu 16.04.6 LTS   4.15.0-1052-gcp   docker://19.3.5
v1-16-worker-2   Ready    <none>   52d   v1.16.4   10.132.0.50   xxxx        Ubuntu 16.04.6 LTS   4.15.0-1052-gcp   docker://19.3.5
v1-16-worker-3   Ready    <none>   20d   v1.16.4   10.132.0.51   xxxx        Ubuntu 16.04.6 LTS   4.15.0-1052-gcp   docker://19.3.5
root@v1-16-master:~# curl 10.132.0.50 2>/dev/null | grep title
<title>Welcome to nginx!</title>
root@v1-16-master:~# kubectl delete po nginx
pod "nginx" deleted
root@v1-16-master:~# curl 10.132.0.50
curl: (7) Failed to connect to 10.132.0.50 port 80: Connection refused

当然，如果我在浏览器上访问公共IP，它也能工作。

Answer 2

更新：

当我写这个答案时，我没有看到问题的编辑部分。考虑到提供的额外信息，这是没有意义的。请置之不理。

原版：

显然，您正在使用的集群在node-port类型服务上安装了入口控制器，而不是load-balancer。为了得到想要的行为，您需要改变入口控制器的配置。请参考用于metalLB案例的nginx入口控制器文档如何做到这一点。