Kubernetes localstack k8s部署yaml和运行状况检查端点

我已经准备好赢10，米尼库比，码头工人。 我需要在本地minikube中启动localstack。我没有发现k8s部署yaml。因此，我采用了docker compose yaml，这是他们在github提供的。并创建如下所示的文件：

# disk volume claim
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  creationTimestamp: null
  labels:
    com.job.service: localstack-claim0
  name: localstack-claim0
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 100Mi
status: {}
---
# service account
apiVersion: v1
kind: ServiceAccount
metadata:
  name: localstack-account
  labels:
    com.job.service: localstack-service-account
---
# service
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: null
  labels:
    com.job.service: localstack-service
  name: localstack-service
spec:
  type: NodePort
  externalTrafficPolicy: Cluster
  ports:
    - name: "edge"
      port: 4566
      targetPort: 4566
    - name: "es"
      port: 4571
      targetPort: 4571
    - name: "ui"
      port: 8080
      targetPort: 8080
  selector:
    com.job.service: localstack-service
status:
  loadBalancer: {}
---
# deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    com.job.service: localstack-deployment
  name: localstack-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      com.job.service: localstack-deployment
  strategy:
    type: Recreate
  template:
    metadata:
      creationTimestamp: null
      labels:
        com.job.service: localstack-deployment
    spec:
      containers:
        - env:
            - name: DATA_DIR
              value: ' '
            - name: DEBUG
              value: ' '
            - name: DOCKER_HOST
              value: tcp://127.0.0.1:2376
            - name: HOST_TMP_FOLDER
            - name: KINESIS_ERROR_PROBABILITY
              value: ' '
            - name: LAMBDA_EXECUTOR
              value: ' '
            - name: PORT_WEB_UI
              value: ' '
            - name: SERVICES
              value: 'sqs'
          image: localstack/localstack
          imagePullPolicy: IfNotPresent
          name: localstack-main
          ports:
            - name: edge
              containerPort: 4566
              protocol: TCP
            - name: es
              containerPort: 4571
              protocol: TCP
            - name: ui
              containerPort: 8080
              protocol: TCP
          livenessProbe:
            failureThreshold: 3
            initialDelaySeconds: 0
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
            httpGet:
              path: /health
              port: edge
          readinessProbe:
            failureThreshold: 3
            initialDelaySeconds: 0
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
            httpGet:
              path: /health
              port: edge
          resources: {}
          volumeMounts:
            - mountPath: /tmp/localstack
              name: localstack-claim0
      restartPolicy: Always
      serviceAccountName: localstack-account
      volumes:
        - name: localstack-claim0
          persistentVolumeClaim:
            claimName: localstack-claim0
status: {}

但当我从kubectl开始时，将-f path_应用到_yaml，并等待所有服务启动。我试图到达运行状况检查端点，但只收到无法连接到主机的异常

我尝试使用minikube隧道，但这没有帮助

可能有人知道如何配置正确的本地设置？我是devops的新手

尝试使用

minikube插件启用入口

，但没有帮助我

尝试使用下一个命令手动暴露和转发端口

kubectl expose pod localstack-deployment-7667b8d6bf-6mqbp --type=ClusterIP --name=localstack

及

---

并与aws cli和awslocal cli连接；但同样的结果是：无法连接

Kubernetes群集需要一个入口控制器，用于将流量从外部世界路由到外部世界

minikube addons enable ingress

以上内容将启用入口，在执行“get pods”操作时，您应该会看到一个有效的入口控制器

NAME                                        READY     STATUS    RESTARTS   AGE
default-http-backend-59868b7dd6-xb8tq       1/1       Running   0          1m
kube-addon-manager-minikube                 1/1       Running   0          3m
kube-dns-6dcb57bcc8-n4xd4                   3/3       Running   0          2m
kubernetes-dashboard-5498ccf677-b8p5h       1/1       Running   0          2m
nginx-ingress-controller-5984b97644-rnkrg   1/1       Running   0          1m
storage-provisioner                         1/1       Running   0          2m

如果这仍然不能解决你的问题， 请发布有关以下kubectl命令的其他信息

kubectl describe ingress
kubectl describe service

---

这些命令的输出可能有助于进一步帮助您

不幸的是没有帮助[！[get pods-A][1][1][1]：[！[Descripte ingress][2][2][2]：[！[Descripte service][3][3]：[！[Descripte service part 2][4][4]：您注意到ingress nginx中的两个pod没有处于就绪状态吗，在它们变为就绪之前，入口服务将不工作，这解释了为什么descripe-ingres命令返回none。试着调试为什么pod没有进入READYHello@faceoff。请检查是否可以直接将kubectl端口转发到pod？我手动尝试使用下一个命令：``kubectl expose pod localstack-deployment-7667b8d6bf-6mqbp--type=ClusterIP--name=localstack``和`kubectl端口转发po/localstack-deployment-7667b8d6bf-6mqbp 4566:4566``然后尝试连接aws cli但总是一样的，无法连接谢意@faceoff。我认为你的案子需要澄清，因为现在有点混乱。您从Minikube开始，但现在还提到了AWS CLI。您能解释一下您到底想要实现什么以及如何实现吗？我想用正确的清单在minikube中启动localstack；Localstack是aws的本地版本，所以我尝试通过AWSCLI访问Localstack

kubectl describe ingress
kubectl describe service