glooctl install gateway长时间未响应

[wwhwwxlz]

Gloo Edge Product

Open Source

Gloo Edge Version

glooctl v1.17.15

Kubernetes Version

1.25.6

Describe the bug

长时间未响应，运行了一晚上还没安装好

Expected Behavior

长时间未响应，运行了一晚上还没安装好

Steps to reproduce the bug

glooctl install gateway
Creating namespace gloo-system... Done.
Starting Gloo Gateway installation...

Additional Environment Detail

No response

Additional Context

No response

[wwhwwxlz]

Gloo failed to install! Detailed logs available at /root/.gloo/debug.log.
Error: installing gloo edge in gateway mode: failed pre-install: 1 error occurred:
* job gateway-certgen failed: BackoffLimitExceeded
[root@master .gloo]# cat /root/.gloo/debug.log
No resources found
No resources found
No resources found
No resources found
serviceaccount "certgen" deleted
No resources found
No resources found
job.batch "gateway-certgen" deleted
No resources found
No resources found

[nfuden]

Can you get the logs from the gateway-certgen job?

[wwhwwxlz]

怎么验证gloo是否成功安装？部署 httpbin 应用程序时无法拉取镜像
Failed to pull image "docker.io/mccutchen/go-httpbin:v2.6.0": rpc error: code = Unknown desc = Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

[danehans]

I could not reproduce this issue:

~ $HOME/.gloo/bin/glooctl version
Server: version undefined, could not find any version of gloo running

{
  "client": {
    "version": "1.17.5"
  },
  "kubernetesCluster": {
    "major": "1",
    "minor": "25",
    "gitVersion": "v1.25.3",
    "buildDate": "2022-10-25T19:38:29Z",
    "platform": "linux/arm64"
  }
}

~ $HOME/.gloo/bin/glooctl install gateway
Creating namespace gloo-system... Done.
Starting Gloo Gateway installation...

Gloo Gateway was successfully installed!

The error you provided indicates that the Kubernetes node failed to pull the httpbin image. I suggest SSH'ing into the node and verifying connectivity to Docker Hub: curl -I https://registry-1.docker.io/v2/.

[wwhwwxlz]

[root@master ~]# kubectl get all -n gloo-system
NAME READY STATUS RESTARTS AGE
pod/discovery-6ddb88d965-brb4t 1/1 Running 0 18m
pod/gateway-proxy-f6d8845db-8vxkc 1/1 Running 0 18m
pod/gloo-7bf897b6bf-l2zzm 1/1 Running 0 18m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/gateway-proxy LoadBalancer 10.105.93.13 80:32506/TCP,443:32221/TCP 18m
service/gloo ClusterIP 10.105.111.253 9977/TCP,9976/TCP,9988/TCP,9966/TCP,9979/TCP,443/TCP 18m

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/discovery 1/1 1 1 18m
deployment.apps/gateway-proxy 1/1 1 1 18m
deployment.apps/gloo 1/1 1 1 18m

NAME DESIRED CURRENT READY AGE
replicaset.apps/discovery-6ddb88d965 1 1 1 18m
replicaset.apps/gateway-proxy-f6d8845db 1 1 1 18m
replicaset.apps/gloo-7bf897b6bf 1 1 1 18m
请问这个怎么验证？
[root@master linux-arm64]#curl $(glooctl proxy url --name gateway-proxy)/all-pets
Error: load balancer ingress not found on service gateway-proxy
curl: (3) URL using bad/illegal format or missing URL
[root@master linux-arm64]# kubectl get svc -n gloo-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
gateway-proxy LoadBalancer 10.105.93.13 80:32506/TCP,443:32221/TCP