docker-使用Ambassador API网关进行微服务

我在让大使正常工作方面遇到一些问题.我是Kubernetes的新手,只是自学.

我已经成功地通过大使提供的演示材料进行了工作-例如/ httpbin /端点运行正常,但是当我尝试部署Go服务时,它就崩溃了.

当点击“ qotm”端点时,这是响应页面：

upstream request timeout

吊舱状态：

CrashLoopBackOff

根据我的研究,它似乎与yaml文件配置不正确有关,但是我正在努力寻找与此用例有关的任何文档.

我的集群在AWS EKS上运行,并且映像已推送到AWS ECR.

main.go：

package main

import (
    "fmt"
    "net/http"
    "os"
)

func main() {
    var PORT string
    if PORT = os.Getenv("PORT"); PORT == "" {
        PORT = "3001"
    }
    http.HandleFunc("/",func(w http.ResponseWriter,r *http.Request) {
        fmt.Fprintf(w,"Hello World from path: %s\n",r.URL.Path)
    })
    http.ListenAndServe(":" + PORT,nil)
}

Dockerfile：

FROM golang:alpine
ADD ./src /go/src/app
WORKDIR /go/src/app
EXPOSE 3001
ENV PORT=3001
CMD ["go","run","main.go"]

test.yaml：

apiVersion: v1
kind: Service
metadata:
  name: qotm
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind:  Mapping
      name:  qotm_mapping
      prefix: /qotm/
      service: qotm
spec:
  selector:
    app: qotm
  ports:
    - port: 80
      name: http-qotm
      targetPort: http-api
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: qotm
spec:
  replicas: 1
  strategy:
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: qotm
    spec:
      containers:
        - name: qotm
          image: ||REMOVED||
          ports:
            - name: http-api
              containerPort: 3001
          readinessProbe:
            httpGet:
              path: /health
              port: 5000
            initialDelaySeconds: 30
            periodSeconds: 3
          resources:
            limits:
              cpu: "0.1"
              memory: 100Mi

吊舱说明：

Name:               qotm-7b9bf4d499-v9nxq
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               ip-192-168-89-69.eu-west-1.compute.internal/192.168.89.69
Start Time:         Sun,17 Mar 2019 17:19:50 +0000
Labels:             app=qotm
                    pod-template-hash=3656908055
Annotations:        <none>
Status:             Running
IP:                 192.168.113.23
Controlled By:      ReplicaSet/qotm-7b9bf4d499
Containers:
  qotm:
    Container ID:   docker://5839996e48b252ac61f604d348a98c47c53225712efd503b7c3d7e4c736920c4
    Image:          IMGURL
    Image ID:       docker-pullable://IMGURL
    Port:           3001/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Sun,17 Mar 2019 17:30:49 +0000
      Finished:     Sun,17 Mar 2019 17:30:49 +0000
    Ready:          False
    Restart Count:  7
    Limits:
      cpu:     100m
      memory:  200Mi
    Requests:
      cpu:        100m
      memory:     200Mi
    Readiness:    http-get http://:3001/health delay=30s timeout=1s period=3s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-5bbxw (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-5bbxw:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-5bbxw
    Optional:    false
QoS Class:       Guaranteed
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                  From                                                  Message
  ----     ------     ----                 ----                                                  -------
  Normal   Scheduled  12m                  default-scheduler                                     Successfully assigned default/qotm-7b9bf4d499-v9nxq to ip-192-168-89-69.eu-west-1.compute.internal
  Normal   Pulled     10m (x5 over 12m)    kubelet,ip-192-168-89-69.eu-west-1.compute.internal  Container image "IMGURL" already present on machine
  Normal   Created    10m (x5 over 12m)    kubelet,ip-192-168-89-69.eu-west-1.compute.internal  Created container
  Normal   Started    10m (x5 over 11m)    kubelet,ip-192-168-89-69.eu-west-1.compute.internal  Started container
  Warning  BackOff    115s (x47 over 11m)  kubelet,ip-192-168-89-69.eu-west-1.compute.internal  Back-off restarting failed container

最佳答案

在您的kubernetes部署文件中,您的应用程序在端口3001上公开了端口5000上的就绪探针,并且在运行容器几次时,我收到了OOMKilled,因此增加了内存限制.无论如何,下面的部署文件应该可以正常工作.

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: qotm
spec:
  replicas: 1
  strategy:
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: qotm
    spec:
      containers:
        - name: qotm
          image: <YOUR_IMAGE>
          imagePullPolicy: Always
          ports:
            - name: http-api
              containerPort: 3001
          readinessProbe:
            httpGet:
              path: /health
              port: 3001
            initialDelaySeconds: 30
            periodSeconds: 3
          resources:
            limits:
              cpu: "0.1"
              memory: 200Mi