GoogleContainerTools / GoogleContainerTools/skaffold
Quickstart: demo app not reachable through localhost
- Langage dominant
- Go
- Étoiles
- 15.9k
- Forks
- 1.7k
- Merge moyen
- 3 j 9 h
- PR mergées (30 j)
- 10
Description
Hello!
I've just been going through the [quickstart](https://skaffold.dev/docs/quickstart/) for Skaffold and had difficulty reaching my example app from my browser at `http://localhost:3000` as the docs describe. However, I did have success reaching the app by using the external IP as output by `kubectl get svc` for the `LoadBalancer` service.
I tried this on two separate laptops as noted in the information section below, a macbook and a Ubuntu machine. So I'm wondering, do I have something misconfigured that would allow `localhost` to work as described, or would it actually be expected that you need to use the external IP for the `LoadBalancer` service?
### Expected behavior
After following the steps outlined in the [quickstart](https://skaffold.dev/docs/quickstart/) through this section:
```
To browse to the web page, open a new terminal and run:
minikube tunnel -p custom
Now open your browser at http://localhost:3000. This displays the content of public/index.html file.
```
Navigating to `http://localhost:3000` displays "Hello World." In the browser.
### Actual behavior
Instead, the browser is unable to connect, but navigating to an external IP as output from `kubectl get svc` successfully loads the page.
I.e.:
```NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 443/TCP 2m39s
web LoadBalancer 10.107.176.91 10.107.176.91 3000:32452/TCP 58s
```
means `10.107.176.91:3000` will succeed.
### Information
- Skaffold version: 2.3.0
- Operating system: macOS Big Sur 11.3.1 & Ubuntu 22.04
- Installed via: skaffold.dev
- Contents of skaffold.yaml:
```yaml
apiVersion: skaffold/v4beta4
kind: Config
metadata:
name: buildpacks-node-tutorial
build:
artifacts:
- image: skaffold-buildpacks-node
buildpacks:
builder: gcr.io/buildpacks/builder:v1
manifests:
rawYaml:
- k8s/web.yaml
```
### Steps to reproduce the behavior
1. `git clone https://github.com/GoogleContainerTools/skaffold`
2. cd skaffold/examples/buildpacks-node-tutorial
3. `skaffold init`
4. Choose the builder to build image skaffold-buildpacks-node Buildpacks (package.json)
5. `minikube start --profile custom`
6. `skaffold config set --global local-cluster true`
7. `eval $(minikube -p custom docker-env)`
8. `skaffold dev`
9. This output appears: Example app listening on port 3000!
10. `minikube tunnel -p custom`
11. Unable to connect to `http://localhost:3000`
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Reproduce the quickstart from examples/buildpacks-node-tutorial using skaffold.yaml, k8s/web.yaml, minikube, and the documented commands through minikube tunnel. Compare the documented localhost:3000 path with the service address from kubectl get svc. Done means the quickstart's expected access method is verified or corrected, with the relevant instructions updated.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- docker, kubernetes
- Domaine
- devops, documentation
- Type d'issue
- Documentation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100