-
Notifications
You must be signed in to change notification settings - Fork 901
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
Unable to view pipelines UI #1931
Comments
check here kubectl edit destinationrule -n kubeflow ml-pipeline |
@rc-coderepo This will make the encryption disabled. We would like to keep using mode ISTIO_MUTUAL. Anyidea how to keep using it ? |
Any updates on this? FYI @johnugeorge @deepak-muley |
@thunderboltsid I have reinstalled kubeflow using v1.3.0 using kustiomize and I did not get this issue. I have installed it on a on-prem kubernetes |
I'm running version: 3dad839. and the suggestion provided by kubeflow/kubeflow#5271 (comment) worked for me but I needed to make sure to restart ALL the pods in the namespace: there was TLS error from the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to inactivity. |
for anyone facing this issue, check this comment: kubeflow/pipelines#5244 (comment) with this you don't need to change the istio destination rules from ISTIO_MUTUAL to DISABLE |
@saumilsdk |
This resolution fixed the same error message I was receiving in my Azure AKS's Kubeflow section Experiment (KFP) . |
Hello,
I am running into this issue while trying to get kubeflow 1.3 running on my kubernetes cluster. All components are deployed successfully (no errors shown in any pod), however, once i pipelines from the centraldashboard i get this error
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: TLS error: 268435703:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER
I think this must be an envoy/istio error any idea what is going wrong? I am using istio version 1.9.3
The text was updated successfully, but these errors were encountered: