rancher / rio

Application Deployment Engine for Kubernetes
https://rio.io
Apache License 2.0
2.27k stars 228 forks source link

local k3d cluster #999

Open matti opened 4 years ago

matti commented 4 years ago

Following https://github.com/rancher/rio/wiki/Local-development-workflow-for-Rio#local-cluster-on-a-mac-with-k3d-and-k3s

I have created

k3d create -n rio --image rancher/k3s:v0.8.1 --publish 80:80 --publish 443:443

then

rio install --ip-address 127.0.0.1

this completes, but shows warning:

Deploying Rio control plane....
Warning: trying to access clusterDomain(http://0l0g70.on-rio.io:31619): Get http://0l0g70.on-rio.io:31619: dial tcp 127.0.0.1:31619: connect: connection refused
rio controller version v0.7.0 (4afd4901) installed into namespace rio-system
Controller logs are available from `rio systemlogs`

Welcome to Rio!

then I run

rio run -p 80:8080 https://github.com/rancher/rio-demo

but once it's up I can't get anything else than 404 from any dns name

$ rio ps
NAME                IMAGE                                     ENDPOINT                                                     PORTS     SCALE     WEIGHT    CREATED         DETAIL
wonderful-neumann   default/wonderful-neumann-v08z87w:f8fab   http://wonderful-neumann-v0-default.ubbn1u.on-rio.io:30114   80:8080   1         100%      2 minutes ago

naturally http://wonderful-neumann-v0-default.ubbn1u.on-rio.io:30114 won't work because port mapping is 80:80, but also:

$ curl wonderful-neumann-v0-default.ubbn1u.on-rio.io:80
404 page not found

what am I doing wrong?

rancher-max commented 4 years ago

@matti I'll update the wiki right now, but try these steps using k3d version v1.5.0:

  1. k3d create -n rio --image rancher/k3s:v1.0.1 --api-port 6550 --publish 80:80 --publish 443:443 --publish 9443:9443 --publish 9080:9080 --workers 1
  2. export KUBECONFIG="$(k3d get-kubeconfig --name='rio')"
  3. kubectl delete service -n kube-system traefik
  4. rio install --ip-address=127.0.0.1 --email your@email.here
  5. rio run -p 80:8080 https://github.com/rancher/rio-demo

Endpoint should become available using svclb instead of nodeport.