使用Glooctl的Glooedge测试路线

发布于 2025-01-25 15:48:53 字数 764 浏览 4 评论 0 原文

任何使用Solo.io的Glooctl命令工作的人。我正在研究Hello World示例, https:https:// docs。 solo.io/gloo--ge/latest/guides/traffic_management/hello_world/

一切顺利,直到最后一步,测试路线规则:

bash%curl $(glooctl prodxy url)/all-pets/all-

pet “错误:在服务网关proxy上找不到负载平衡器入口 curl:(3)使用不良/非法格式或缺少URL的URL“

我试图将我认为是Gloo的“代理URL”放置:

bash% curl $(glooctl gloo-system-gateway-proxy-8080)/all-pets

bash%curl $(gloo-system-gatestemway-gateway-proxy-8080)/all-pets 错误:未知命令“ gloo-system-gateway-proxy-8080” for“ glooctl”,

因此不喜欢诸如“代理URL”之类的逻辑命令,并且不喜欢它 采用实际的代理网址。

有人打了这场战斗并赢了吗?

tia

Anyone worked with solo.io's glooctl command. I was working on the hello world example, https://docs.solo.io/gloo-edge/latest/guides/traffic_management/hello_world/

and everything went smoothly until the last step, testing the route rule:

bash % curl $(glooctl proxy url)/all-pets

which returns, "Error: load balancer ingress not found on service gateway-proxy
curl: (3) URL using bad/illegal format or missing URL"

I tried putting what I thought was Gloo's "proxy url":

bash% curl $(glooctl gloo-system-gateway-proxy-8080)/all-pets

and bash% curl $(gloo-system-gateway-proxy-8080)/all-pets
Error: unknown command "gloo-system-gateway-proxy-8080" for "glooctl"

So it doesn't like logical commands like "proxy url" and it doesn't
take the actual proxy url.

Anyone fought this battle and won?

TIA

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

分开我的手 2025-02-01 15:48:53

我使用Minikube,问题是外部IP 待处理状态中。

Minikube隧道解决了问题。

glooctl代理URL

错误:在Service Gateway-Proxy上找不到加载平衡器入口

kubectl get svc -n gloo-system

NAME            TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                               AGE
gateway         ClusterIP      10.102.152.223   <none>        443/TCP                               49m
gateway-proxy   LoadBalancer   10.102.171.136   <pending>     80:30439/TCP,443:32178/TCP            49m
gloo            ClusterIP      10.97.145.90     <none>        9977/TCP,9976/TCP,9988/TCP,9979/TCP   49m


kubernetes服务外部IP待处理

I use minikube, the problem is that EXTERNAL-IP is in pending state.

minikube tunnel solve the problem.

glooctl proxy url

Error: load balancer ingress not found on service gateway-proxy

kubectl get svc -n gloo-system

NAME            TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                               AGE
gateway         ClusterIP      10.102.152.223   <none>        443/TCP                               49m
gateway-proxy   LoadBalancer   10.102.171.136   <pending>     80:30439/TCP,443:32178/TCP            49m
gloo            ClusterIP      10.97.145.90     <none>        9977/TCP,9976/TCP,9988/TCP,9979/TCP   49m

https://makeoptim.com/en/service-mesh/kubernetes-external-ip-pending
Kubernetes service external ip pending

谁许谁一生繁华 2025-02-01 15:48:53

我相信该命令是 curl $(glooctl代理URL)/all-pets; glooctl代理url 返回什么?

I believe the command is curl $(glooctl proxy url)/all-pets; what does glooctl proxy url return for you?

伪心 2025-02-01 15:48:53

解决方案@NorthMorn提供的工作正常,Minikube上的命令与 Minikube隧道一样简单。谢谢@northmorn。

The solution @northmorn provided works just fine, and the command on minikube is as simple as minikube tunnel. Thanks @Northmorn.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文