ssl - Spinnaker 服务在 HTTPS 配置后未启动

Question

我按照 https://www.spinnaker.io/setup/security/ssl/#server-terminated-ssl 遵循了 spinnaker HTTPS 配置

在 spinnaker 服务回显之后，front50 和 igor 无法正常启动，输出低于输出。

kubectl get po -n spinnaker
NAME                                READY   STATUS             RESTARTS   AGE
spin-clouddriver-5cd79d98d6-bhd4s   0/1     Evicted            0          3h34m
spin-clouddriver-5cd79d98d6-srnwl   1/1     Running            0          9m54s
spin-deck-5bd984bd9c-cx6xn          1/1     Running            0          3h34m
spin-echo-84848bfc46-2hwml          0/1     Running            219        17h
spin-echo-866c54bb8d-p4qbs          0/1     CrashLoopBackOff   37         3h34m
spin-front50-686f577f79-xld6d       0/1     Running            218        17h
spin-front50-988ccc789-662kn        0/1     Running            39         3h34m
spin-gate-5954b6cd88-rzqmd          1/1     Running            0          3h34m
spin-igor-5c8bd8c694-lr7z6          0/1     Running            226        17h
spin-igor-fd97cd9f6-q5wfs           0/1     Running            41         3h34m
spin-orca-546d5685dc-wswkj          1/1     Running            8          3h34m
spin-redis-58d4d69d77-st4bk         1/1     Running            0          29d
spin-rosco-fd6f6596d-2ht9r          1/1     Running            0          3h34m

回声服务

kubectl describe po -n spinnaker spin-echo-84848bfc46-2hwml

Warning  Unhealthy  5m35s (x1648 over 18h)  kubelet, aks-agentpool-30093549-vmss000015  Readiness probe failed:

Front50 服务

kubectl describe po -n spinnaker spin-front50-988ccc789-662kn

Warning  Unhealthy  77s (x866 over 3h51m)  kubelet, aks-agentpool-30093549-vmss000014  Readiness probe failed: wget: can't connect to remote host (127.0.0.1): Connection refused

伊戈尔服务

kubectl describe po -n spinnaker spin-igor-fd97cd9f6-q5wfs

Warning  Unhealthy  17m (x558 over 3h52m)    kubelet, aks-agentpool-30093549-vmss000015  Readiness probe failed: wget: can't connect to remote host (127.0.0.1): Connection refused

Front50 日志在“扫描 api 列表引用”后停止，然后重新启动

2020-01-09 09:29:11.974  INFO 1 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2020-01-09 09:29:20.526  INFO 1 --- [           main] d.s.w.p.DocumentationPluginsBootstrapper : Context refreshed
2020-01-09 09:29:20.894  INFO 1 --- [           main] d.s.w.p.DocumentationPluginsBootstrapper : Found 1 custom documentation plugin(s)
2020-01-09 09:29:22.149  INFO 1 --- [           main] s.d.s.w.s.ApiListingReferenceScanner     : Scanning for api listing references

Echo 服务日志显示，它失败了，因为无法连接到 front50 服务

Caused by: java.net.ConnectException: Failed to connect to spin-front50.spinnaker/ipAddress:8080

同样 Igor 服务日志显示，它失败了，因为无法连接到 echo 服务

Caused by: java.net.ConnectException: Failed to connect to spin-echo.spinnaker/ipAddress:8089

我尝试增加 liveness probe hal config deploy edit --liveness-probe-enabled true --liveness-probe-initial-delay-seconds 180 但还是一样。

其他front50服务日志，不确定是否相关

2020-01-09 09:37:32.066  INFO 1 --- [           main] i.g.r.utils.RxJava2OnClasspathCondition  : RxJava2 related Aspect extensions are not activated, because RxJava2 is not on the classpath.
2020-01-09 09:37:32.067  INFO 1 --- [           main] i.g.r.utils.ReactorOnClasspathCondition  : Reactor related Aspect extensions are not activated because Reactor is not on the classpath.

Spinnaker 已正确连接到 Azure 存储，因为它需要 front50 服务。当我执行 hal config storage azs 时，我得到配置存储的响应

+ Get current deployment
  Success
+ Get persistent store
  Success
+ Successfully got persistent store "azs".
AzsPersistentStore(storageAccountName=xxx, storageAccountKey=xxx, storageContainerName=xxx)

请指教。谢谢。

Answer 1

我再次将 --liveness-probe-initial-delay-seconds 增加到 600 秒，然后它开始工作。