epinio: V1.0.0: Port-forward not working
Describe the bug
The epinio app port-forward
is not working with v1.0.0. It doesn’t open the port and ends up with a generic error (see below)
To Reproduce Steps to reproduce the behavior, e.g.:
- Install Epinio
- Push the app:
epinio push -n app1
- Create a new port-forward:
epinio app port-forward app1 8088:8080
- Results in error:
❌ error port forwarding to application: error upgrading connection:
Expected behavior The port-forward should run successfully and the application would be accessible through the port opened.
Logs Here are the logs from the command output with the trace level at 255
export TRACE_LEVEL=255
2022/07/15 10:35:21 Settings-0xc000914160: "level"=4 "msg"="Loading" "from"="/home/corsair/.config/epinio/settings.yaml"
2022/07/15 10:35:21 Settings-0xc000914160: "level"=4 "msg"="Loaded" "value"="namespace=(workspace), user=(admin), pass=(password), api=(https://epinio.127.0.0.1.sslip.io), wss=(wss://epinio.127.0.0.1.sslip.io), color=(true), appchart=(), @(/home/corsair/.config/epinio/settings.yaml)"
2022/07/15 10:35:21 EpinioClient/NewEpinioClient: "level"=4 "msg"="Ingress API" "url"="https://epinio.127.0.0.1.sslip.io"
2022/07/15 10:35:21 EpinioClient/NewEpinioClient: "level"=4 "msg"="Settings API" "url"="https://epinio.127.0.0.1.sslip.io"
2022/07/15 10:35:21 EpinioClient/Apps: "level"=4 "msg"="start" "Namespace"="workspace" "Application"="mysimpleapp"
Executing port forwarding
Namespace: workspace
Application: mysimpleapp
2022/07/15 10:35:21 EpinioApiClient: "level"=4 "msg"="GET https://epinio.127.0.0.1.sslip.io/api/v1/authtoken"
2022/07/15 10:35:22 EpinioApiClient: "level"=5 "msg"="request finished" "method"="GET" "uri"="https://epinio.127.0.0.1.sslip.io/api/v1/authtoken" "body"=""
2022/07/15 10:35:22 EpinioApiClient: "level"=5 "msg"="response received" "status"=200 "header"={"Content-Length":["466"],"Content-Type":["application/json; charset=utf-8"],"Date":["Fri, 15 Jul 2022 08:35:21 GMT"],"Set-Cookie":["epinio-session=MTY1Nzg3NDEyMXxEdi1CQkFFQ180SUFBUkFCRUFBQV81UF9nZ0FCQm5OMGNtbHVad3dHQUFSMWMyVnlLMmRwZEdoMVlpNWpiMjB2WlhCcGJtbHZMMlZ3YVc1cGJ5OXBiblJsY201aGJDOWhkWFJvTGxWelpYTF9nd01CQVFSVmMyVnlBZi1FQUFFRkFRaFZjMlZ5Ym1GdFpRRU1BQUVJVUdGemMzZHZjbVFCREFBQkNVTnlaV0YwWldSQmRBSF9oZ0FCQkZKdmJHVUJEQUFCQ2s1aGJXVnpjR0ZqWlhNQl80Z0FBQUFRXzRVRkFRRUVWR2x0WlFIX2hnQUFBQmJfaHdJQkFRaGJYWE4wY21sdVp3SF9pQUFCREFBQUlfLUVJQUVGWVdSdGFXNENEd0VBQUFBTzJtSF9mQUFBQUFBQUFBRUZZV1J0YVc0QXyFYUWH8BhFTyJB3hu73n5ZpBwUHvvmuyqpnik7eXHUpw==; Expires=Sun, 17 Jul 2022 08:35:21 GMT; Max-Age=172800; HttpOnly; Secure"]} "TLSServerName"="epinio.127.0.0.1.sslip.io" "body"="{\"token\":\"eyJhbGciOiJSUzM4NCIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJlcGluaW8tc2VydmVyIiwiZXhwIjoxNjU3ODc0MTUxLCJ1c2VyIjoiYWRtaW4ifQ.NICfXXm3Xi0FG-PG_nRaSc_6eXm1dElBMLu2c125Gd9K43TjKSauFE80f2lhxeVgpJyPMNXwsNhcZCP6qMdMsW5XHVoaLKWkPt-X_CcNUS6iJQdg68LjW19T7c3EPbrGNeX6hhVp8xyCQh-clxA3MmHQWEb6E_FtV034tH6hqzaXRVUe1L180xyAC2bjzfE7i9b_82NWI-4F73hmaXFDVjEaHHWiHav2RA7QTLvxCfPeLrkg2KJg9FC7dq3Flen3x4J1BUkRHzScUyl4yt0QAwir3m0CTZbKjuC_DJ7DUdZonUX55NmXbZPgkc9lEY_zhPf0zy4Y2RwvDb-DJOp6aQ\"}"
2022/07/15 10:35:22 EpinioClient/Apps: "level"=4 "msg"="return" "Namespace"="workspace" "Application"="mysimpleapp"
❌ error port forwarding to application: error upgrading connection:
To follow the server logs you can use:
kubectl logs -n epinio -l app.kubernetes.io/name=epinio-server -c epinio-server -f
Epinio version: v1.0.0
listening on localhost on port 8030
2022/07/15 08:02:16 http: proxy error: http2: invalid Upgrade request header: ["SPDY/3.1"]
Cluster (please complete the following information):
- Provider: [e.g. K3D, minikube, KinD, AKS, EKS, GKE, RKE, …]
- Options: [e.g. number of nodes, storageclasses, loadbalancer if customised]
- Kubernetes Version: [e.g. 1.20]
Desktop/CLI (please complete the following information):
- OS: Linux OpenSUSE Tumbleweed
- K8s cluster: Rancher Desktop 1.4.1
- Epinio Version: 1.0.0
- Epinio Install Options: N/A
Additional context N/A
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (14 by maintainers)
The port forwarding command does not end by design. The moment you end that command the port forwarding ends. In other words, that is correct behaviour, as far as I know - @enrichman
Agreed, to me this looks to be a kubernetes/RD issue.
I managed to reproduce the issue on MAC.
Steps as described in the description above:
example-12factor
epinio push -n app1
// The app should load correctlyepinio app port-forward app1 8088:8080
❌ error port forwarding to application: error upgrading connection
Got the info that @mmartin24 managed to reproduce using Rancher Desktop on Mac.