1

笔记

我正在尝试将演示服务的服务和入口（从“Kubernetes in Action”）部署到traefik已安装 Helm 的 AWS EKS 集群。

traefik.example.com在手动将 AWS ELB 的 IP 地址添加traefik到本地/etc/hosts文件中的该主机名后，我可以从主机名访问 traefik 仪表板。

如果我描述的服务和入口traefik-dashboard：

$ kubectl describe svc -n kube-system traefik-dashboard
Name:              traefik-dashboard
Namespace:         kube-system
Labels:            app=traefik
                   chart=traefik-1.52.6
                   heritage=Tiller
                   release=traefik
Annotations:       <none>
Selector:          app=traefik,release=traefik
Type:              ClusterIP
IP:                10.100.164.81
Port:              <unset>  80/TCP
TargetPort:        8080/TCP
Endpoints:         172.31.27.70:8080
Session Affinity:  None
Events:            <none>

$ kubectl describe ing -n kube-system traefik-dashboard
Name:             traefik-dashboard
Namespace:        kube-system
Address:
Default backend:  default-http-backend:80 (<none>)
Rules:
Host                 Path  Backends
----                 ----  --------
traefik.example.com
                        traefik-dashboard:80 (172.31.27.70:8080)
Annotations:
Events:  <none>

服务和入口控制器似乎正在使用命名空间中正在运行的traefik-575cc584fb-v4mfnpod kube-system。

鉴于此信息并查看 traefik 文档，我尝试使用以下 YAML 通过其入口公开演示服务：

apiVersion: apps/v1beta2
kind: ReplicaSet
metadata:
name: kubia
spec:
replicas: 3
selector:
    matchLabels:
    app: kubia
template:
    metadata:
    labels:
        app: kubia
    spec:
    containers:
    - name: kubia
        image: luksa/kubia

---

apiVersion: v1
kind: Service
metadata:
name: kubia
namespace: default
spec:
selector:
    app: traefik
    release: traefik
ports:
- name: web
    port: 80
    targetPort: 8080

---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: kubia
namespace: default
spec:
rules:
- host: kubia.int
    http:
    paths:
    - path: /
        backend:
        serviceName: kubia
        servicePort: web

应用此功能后，在手动将 AWS ELB 的 IP 地址添加到本地文件中的该主机名后，我无法kubia从该主机名访问该服务。相反，我得到了回应。描述创建的资源会显示一些不同的信息。kubia.inttraefik/etc/hostsService Unavailable

$ kubectl describe svc kubia
Name:              kubia
Namespace:         default
Labels:            <none>
Annotations:       kubectl.kubernetes.io/last-applied-configuration:
                    {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"kubia","namespace":"default"},"spec":{"ports":[{"name":"web","por...
Selector:          app=traefik,release=traefik
Type:              ClusterIP
IP:                10.100.142.243
Port:              web  80/TCP
TargetPort:        8080/TCP
Endpoints:         <none>
Session Affinity:  None
Events:            <none>

$ kubectl describe ing kubia
Name:             kubia
Namespace:        default
Address:
Default backend:  default-http-backend:80 (<none>)
Rules:
Host       Path  Backends
----       ----  --------
kubia.int
            /   kubia:web (<none>)
Annotations:
kubectl.kubernetes.io/last-applied-configuration:  {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{},"name":"kubia","namespace":"default"},"spec":{"rules":[{"host":"kubia.int","http":{"paths":[{"backend":{"serviceName":"kubia","servicePort":"web"},"path":"/"}]}}]}}

Events:  <none>

我还注意到演示kubia服务没有端点，并且相应的入口显示没有可用的后端。

我注意到的另一件事是演示kubia服务和入口在default命名空间中，而traefik-dashboard服务和入口在kube-system命名空间中。

有什么东西会跳出来吗？关于诊断它的最佳方法的任何建议？

提前谢谢了！

4

1 回答 1

1

似乎您缺少kubernetes.io/ingress.class: traefik告诉您的 Traefik 入口控制器为该入口定义服务的那个。

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kubia
  namespace: default
  annotations:
    kubernetes.io/ingress.class: traefik
spec:
rules:
- host: kubia.int
    http:
    paths:
    - path: /
        backend:
        serviceName: kubia
        servicePort: web

如果您查看文档中的示例，您会发现唯一没有注释的 Ingress 是traefik-web-ui指向 Traefik Web UI。

于 2018-11-13T22:23:58.113 回答