在kubernetes上安装spinnaker时出错
我按照实验性的k8s安装，在打开门户之前，它似乎一直在工作。然后，应用程序和项目有标题栏，但主页体只是一个旋转装置。我如何调试这个 安装说明： 以下是我在日志中发现的唯一错误：在kubernetes上安装spinnaker时出错,kubernetes,spinnaker,Kubernetes,Spinnaker,我按照实验性的k8s安装，在打开门户之前，它似乎一直在工作。然后，应用程序和项目有标题栏，但主页体只是一个旋转装置。我如何调试这个 安装说明： 以下是我在日志中发现的唯一错误： 2017-09-12 19:29:35.764 INFO 1 --- [x-credentials-1] c.n.s.g.s.internal.ClouddriverService : ---- ERROR http://spin-clouddriver.spinnaker:7002/credentials 20
2017-09-12 19:29:35.764 INFO 1 --- [x-credentials-1] c.n.s.g.s.internal.ClouddriverService : ---- ERROR http://spin-clouddriver.spinnaker:7002/credentials
2017-09-12 19:29:35.765 INFO 1 --- [x-credentials-1] c.n.s.g.s.internal.ClouddriverService : java.net.SocketTimeoutException: connect timed out
kubectl describe svc --namespace spinnaker spin-clouddriver
Name: spin-clouddriver
Namespace: spinnaker
Labels: app=spin
stack=clouddriver
Annotations: <none>
Selector: load-balancer-spin-clouddriver=true
Type: ClusterIP
IP: 100.70.137.138
Port: <unset> 7002/TCP
Endpoints: 100.96.2.4:7002
Session Affinity: None
Events: <none>
kubectl describe pod --namespace spinnaker spin-clouddriver-v000-fmwhr
Name: spin-clouddriver-v000-fmwhr
Namespace: spinnaker
Node: ip-172-20-61-85.ca-central-1.compute.internal/172.20.61.85
Start Time: Wed, 13 Sep 2017 08:11:05 -0400
Labels: load-balancer-spin-clouddriver=true
replication-controller=spin-clouddriver-v000
Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"spinnaker","name":"spin-clouddriver-v000","uid":"9df7c363-987c-11e7-90ae-02f58db8...
Status: Running
IP: 100.96.2.4
Created By: ReplicaSet/spin-clouddriver-v000
Controlled By: ReplicaSet/spin-clouddriver-v000
Containers:
clouddriver:
Container ID: docker://d7c7ba2611186a248f6910c605c71045e0f7300f3ab4857df30ef28b9f9c7f54
Image: quay.io/spinnaker/clouddriver:master
Image ID: docker-pullable://quay.io/spinnaker/clouddriver@sha256:98be0ee63e040a2bcd8ba6ca6a67d23bb8aab457f4a86882b3da65f043dc895f
Port: 7002/TCP
State: Running
Started: Wed, 13 Sep 2017 08:12:03 -0400
Ready: True
Restart Count: 0
Readiness: http-get http://:7002/credentials delay=20s timeout=1s period=10s #success=1 #failure=3
Environment: <none>
Mounts:
/opt/spinnaker/config from spinnaker-config (rw)
/root/.kube from creds-config (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-hpql5 (ro)
Conditions:
Type Status
Initialized True
Ready True
PodScheduled True
Volumes:
spinnaker-config:
Type: Secret (a volume populated by a Secret)
SecretName: spinnaker-config
Optional: false
creds-config:
Type: Secret (a volume populated by a Secret)
SecretName: creds-config
Optional: false
default-token-hpql5:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-hpql5
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.alpha.kubernetes.io/notReady:NoExecute for 300s
node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
19m 19m 1 default-scheduler Normal Scheduled Successfully assigned spin-clouddriver-v000-fmwhr to ip-172-20-61-85.ca-central-1.compute.internal
19m 19m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "creds-config"
19m 19m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "default-token-hpql5"
19m 19m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "spinnaker-config"
19m 19m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver} Normal Pulling pulling image "quay.io/spinnaker/clouddriver:master"
18m 18m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver} Normal Pulled Successfully pulled image "quay.io/spinnaker/clouddriver:master"
18m 18m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver} Normal Created Created container
18m 18m 1 kubelet, ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver} Normal Started Started container
18m 18m 2 kubelet, ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver} Warning Unhealthy Readiness probe failed: Get http://100.96.2.4:7002/credentials: dial tcp 100.96.2.4:7002: getsockopt: connection refused
kubectl description svc——名称空间spinnaker spin clouddriver
名称：spin clouddriver
名称空间：spinnaker
标签：app=spin
stack=clouddriver
注释：
选择器：负载平衡器spin clouddriver=true
类型：集群
IP:100.70.137.138
端口：7002/TCP
终点：100.96.2.4:7002
会话关联：无
活动：
kubectl描述pod——名称空间spinnaker spin-clouddriver-v000-fmwhr
名称：spin-clouddriver-v000-fmwhr
名称空间：spinnaker
节点：ip-172-20-61-85.ca-central-1.compute.internal/172.20.61.85
开始时间：2017年9月13日星期三08:11:05-0400
标签：负载平衡器spin clouddriver=true
复制控制器=spin-clouddriver-v000
注释：kubernetes.io/创建人={“种类”：“SerializedReference”，“apiVersion”：“v1”，“reference”：{“种类”：“ReplicaSet”，“命名空间”：“spinnaker”，“名称”：“spin-clouddriver-v000”，“uid”：“9df7c363-987c-11e7-90ae-02f58db8…”。。。
状态：正在运行
IP:100.96.2.4
创建人：ReplicaSet/spin-clouddriver-v000
控制人：ReplicaSet/spin-clouddriver-v000
容器：
云驱动程序：
容器ID:docker://d7c7ba2611186a248f6910c605c71045e0f7300f3ab4857df30ef28b9f9c7f54
图片：quay.io/spinnaker/clouddriver:master
图像ID:docker-pullable://quay.io/spinnaker/clouddriver@sha256:98be0ee63e040a2bcd8ba6ca6a67d23bb8aab457f4a86882b3da65f043dc895f
端口：7002/TCP
状态：正在运行
开始时间：2017年9月13日星期三08:12:03-0400
准备好了吗
重新启动计数：0
准备就绪：http get http://:7002/凭证延迟=20s超时=1s周期=10s成功=1失败=3
环境：
挂载：
/来自spinnaker配置（rw）的opt/spinnaker/config
/creds配置（rw）中的root/.kube
/来自default-token-hpql5（ro）的var/run/secrets/kubernetes.io/serviceCount
条件：
类型状态
初始化为True
准备好了吗
播客预定为真
卷数：
spinnaker配置：
类型：Secret（由Secret填充的卷）
SecretName:spinnaker配置
可选：false
creds配置：
类型：Secret（由Secret填充的卷）
SecretName:creds配置
可选：false
default-token-hpql5：
类型：Secret（由Secret填充的卷）
SecretName:default-token-hpql5
可选：false
QoS等级：最佳努力
节点选择器：
容差：node.alpha.kubernetes.io/notReady:NoExecute持续300秒
node.alpha.kubernetes.io/不可访问：不执行300秒
活动：
子对象路径类型原因消息中的FirstSeen LastSeen计数
--------- -------- ----- ---- ------------- -------- ------ -------
19m 19m 1默认调度程序正常调度成功将spin-clouddriver-v000-fmwhr分配给ip-172-20-61-85.ca-central-1.compute.internal
19m 19m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal Normal SuccessfulMountVolume装入卷。卷“creds config”的安装成功
19m 19m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal Normal SuccessfulMountVolume装入卷。卷“default-token-hpql5”的安装成功
19m 19m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal Normal SuccessfulMountVolume装入卷。卷“spinnaker配置”的安装成功
19m 19m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver}正常拉动图像“码头io/spinnaker/clouddriver:master”
18m 18m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver}正常拉取成功拉取图像“码头io/spinnaker/clouddriver:master”
18m 18m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver}正常创建的容器
18m 18m 1 kubelet，ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver}正常已启动容器
18m 18m 2 kubelet，ip-172-20-61-85.ca-central-1.compute.internal spec.containers{clouddriver}警告不正常就绪探测失败：获取http://100.96.2.4:7002/credentials: 拨打tcp 100.96.2.4:7002:getsockopt:连接被拒绝
可以找到安装说明。Spinnaker的安装在过去一年中有了显著的改进。他们现在有一个名为的工具，用于配置和部署Spinnaker 它可以直接部署到Kubernetes集群中
可以找到安装说明。我按照说明在k8s上安装Spinnaker。它工作正常。我想你可以按照说明在k8s上安装Spinnaker。我按照说明在k8s上安装Spinnaker。它工作正常。我想你可以按照说明在k8s上安装Spinnaker。看起来没有云驱动程序的服务连接。您可以使用
kubectl description