You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Falta un poco de contexto aquí. Entiendo que Minikube solo crea un servicio automáticamente cuando se crea el clúster, y ese servicio es el "default". Si has creado un servicio personalizado, por favor proporciona más detalles utilizando comandos como describe, etc.
% minikube service --all
|-----------|------------|-------------|--------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|-----------|------------|-------------|--------------|
| default | kubernetes | | No node port |
|-----------|------------|-------------|--------------|
Los comandos necesarios para reproducir la incidencia: minikube service facturador-prueba
El resultado completo del comando que ha fallado:
stderr:
I0506 12:40:37.913042 15191 ssh_runner.go:195] Run: ls
I0506 12:40:37.915758 15191 api_server.go:253] Checking apiserver healthz at https://192.168.49.2:8443/healthz ...
I0506 12:40:37.919552 15191 api_server.go:279] https://192.168.49.2:8443/healthz returned 200:
ok
I0506 12:40:37.919568 15191 host.go:66] Checking if "minikube" exists ...
I0506 12:40:37.919847 15191 cli_runner.go:164] Run: docker container inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}},{{.GlobalIPv6Address}}{{end}}" minikube
I0506 12:40:37.969369 15191 service.go:214] Found service: &Service{ObjectMeta:{facturador-prueba default 4eb23c4d-cfdc-4806-a9c8-323de3f2ce58 1658 0 2024-05-06 12:39:34 +0200 CEST map[app:facturador-prueba] map[] [] [] [{kubectl-expose Update v1 2024-05-06 12:39:34 +0200 CEST FieldsV1 {"f:metadata":{"f:labels":{".":{},"f:app":{}}},"f:spec":{"f:externalTrafficPolicy":{},"f:internalTrafficPolicy":{},"f:ports":{".":{},"k:{"port":8080,"protocol":"TCP"}":{".":{},"f:port":{},"f:protocol":{},"f:targetPort":{}}},"f:selector":{},"f:sessionAffinity":{},"f:type":{}}} }]},Spec:ServiceSpec{Ports:[]ServicePort{ServicePort{Name:,Protocol:TCP,Port:8080,TargetPort:{0 8080 },NodePort:32106,AppProtocol:nil,},},Selector:map[string]string{app: facturador-prueba,},ClusterIP:10.108.218.124,Type:NodePort,ExternalIPs:[],SessionAffinity:None,LoadBalancerIP:,LoadBalancerSourceRanges:[],ExternalName:,ExternalTrafficPolicy:Cluster,HealthCheckNodePort:0,PublishNotReadyAddresses:false,SessionAffinityConfig:nil,IPFamilyPolicy:*SingleStack,ClusterIPs:[10.108.218.124],IPFamilies:[IPv4],AllocateLoadBalancerNodePorts:nil,LoadBalancerClass:nil,InternalTrafficPolicy:*Cluster,TrafficDistribution:nil,},Status:ServiceStatus{LoadBalancer:LoadBalancerStatus{Ingress:[]LoadBalancerIngress{},},Conditions:[]Condition{},},}
I0506 12:40:37.973224 15191 host.go:66] Checking if "minikube" exists ...
I0506 12:40:37.973522 15191 cli_runner.go:164] Run: docker container inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}},{{.GlobalIPv6Address}}{{end}}" minikube
I0506 12:40:38.009386 15191 out.go:177] * Opening service default/facturador-prueba in default browser...
I0506 12:40:44.744034 15191 out.go:177]
W0506 12:40:44.748502 15191 out.go:239] X Exiting due to HOST_BROWSER: open url failed: [default facturador-prueba 8080 http://192.168.49.2:32106]: exit status 4
W0506 12:40:44.748534 15191 out.go:239] *
W0506 12:40:44.750042 15191 out.go:239] ╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run
minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. ││ * Please also attach the following file to the GitHub issue: │
│ * - /tmp/minikube_service_bcc29b78159d429103db4e013e8c5480b1333295_0.log │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0506 12:40:44.753326 15191 out.go:177]
El resultado del comando
minikube logs
:La versión del sistema operativo que utilizaste: ubuntu 22.04 lts
logs_2.txt
The text was updated successfully, but these errors were encountered: