We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I followed the instructions for the NodePort example: https://k3d.io/v5.6.0/usage/exposing_services/
I got the standard nginX page which was to be expected.
But following the instructions for the Ingress example, I don't get the same result as for the NodePort example.
k3d cluster delete k3s-default
k3d cluster create --api-port 6550 -p "8081:80@loadbalancer" --agents 2
docker ps -a
kubectl create deployment nginx --image=nginx
kubectl create service clusterip nginx --tcp=80:80
less thatfile.yaml
kubectl apply -f thatfile.yaml
The expectation is that I run the following, and I should get something like the NodePort example.
The expectation is that I run the following, and I should get something like the NodePort example, but instead I get 'empty reply'
curl localhost:8081/
For the browser, the NodePort example works as expected, but the Ingress example doesn't.
http://localhost:8081/
k3d runtime-info
k3d
k3d version
docker version
docker info
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What did you do
I followed the instructions for the NodePort example:
https://k3d.io/v5.6.0/usage/exposing_services/
I got the standard nginX page which was to be expected.
But following the instructions for the Ingress example, I don't get the same result as for the NodePort example.
k3d cluster delete k3s-default
k3d cluster create --api-port 6550 -p "8081:80@loadbalancer" --agents 2
docker ps -a
kubectl create deployment nginx --image=nginx
kubectl create service clusterip nginx --tcp=80:80
less thatfile.yaml
kubectl apply -f thatfile.yaml
What did you expect to happen
The expectation is that I run the following, and I should get something like the NodePort example.
Screenshots or terminal output
The expectation is that I run the following, and I should get something like the NodePort example, but instead I get 'empty reply'
curl localhost:8081/
For the browser, the NodePort example works as expected, but the Ingress example doesn't.
http://localhost:8081/
Which OS & Architecture
k3d runtime-info
Which version of
k3d
k3d version
Which version of docker
docker version
docker info
The text was updated successfully, but these errors were encountered: