aws-eks上的spring引导和helm图表

ljo96ir5  于 2021-07-13  发布在  Java
关注(0)|答案(0)|浏览(229)

当我使用helmchart在aws eks上部署spring-boot应用程序时。我遇到以下错误,不确定是否缺少aws eks上的某些配置:

│   Type     Reason            Age                  From                                                     Message                                                                                           │
│   ----     ------            ----                 ----                                                     -------                                                                                           │
│   Warning  FailedScheduling  18m                  default-scheduler                                        0/1 nodes are available: 1 node(s) didn't match pod affinity/anti-affinity, 1 node(s) didn't sati │
│ sfy existing pods anti-affinity rules.                                                                                                                                                                       │
│   Normal   Scheduled         18m                  default-scheduler                                        Successfully assigned tee/*****-services-576d5cddfd-vfls4 to ip-192-168-8-0.ap-southeast-1.comput │
│ e.internal                                                                                                                                                                                                   │
│   Normal   Pulling           18m                  kubelet, ip-192-168-8-0.ap-southeast-1.compute.internal  Pulling image "061424976585.dkr.ecr.ap-southeast-1.amazonaws.com/*****/*****-service:1.0.0-SNAPSH │
│ OT-69c97"                                                                                                                                                                                                    │
│   Normal   Pulled            18m                  kubelet, ip-192-168-8-0.ap-southeast-1.compute.internal  Successfully pulled image "061424976585.dkr.ecr.ap-southeast-1.amazonaws.com/*****/*****-service: │
│ 1.0.0-SNAPSHOT-69c97"                                                                                                                                                                                        │
│   Normal   Created           18m                  kubelet, ip-192-168-8-0.ap-southeast-1.compute.internal  Created container*****-services                                                                  │
│   Normal   Started           18m                  kubelet, ip-192-168-8-0.ap-southeast-1.compute.internal  Started container*****-services                                                                  │
│   Warning  Unhealthy         3m2s (x60 over 17m)  kubelet, ip-192-168-8-0.ap-southeast-1.compute.internal  Readiness probe failed: HTTP probe failed with statuscode: 503

实际上我对此一无所知。把这个问题贴在这里,希望能有人熟悉spring boot和eks知道根本原因。先谢谢你。

暂无答案!

目前还没有任何答案,快来回答吧!

相关问题