-
Notifications
You must be signed in to change notification settings - Fork 718
New issue
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
Dialer is broken in e2e tests #1273
Comments
This happens when using The custom dev port forwarder expects that a pod address is composed of three parts cloud-on-k8s/operators/pkg/dev/portforward/pod_forwarder.go Lines 118 to 124 in 03fad11
|
I guess we can either:
I'd vote for 2. |
Do not we also need the namespace? |
Our quickstart doc advertises reaching the service from its name only (no namespace, no
However this longer-term E2E tests will probably work across multiple namespaces I guess it's fine to include the namespace here. With no namespace it's almost impossible to know where to redirect the call from the custom dialer code perspective anyway. tl;dr: you're right 👍 |
dialer
is broken in e2e tests.I think it comes from e1a3023#diff-fcadcd8abc54d908e7568bc91579f44fL31
The namespace is needed in the url in order to get the pod with the
RESTClient
and without thesvc
it's trying to forward to a pod and not to a service.The text was updated successfully, but these errors were encountered: