-
Notifications
You must be signed in to change notification settings - Fork 3
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
ml-pipeline-metadata-grpc-server and MySQL connection with mysql_native_password? #13
Comments
Hey, about the kubeflow/pipelines#9549 (comment) About the istio and certificates:
|
Hi @kromanow94 , Thank you very much for the reply. Regarding Regarding Istio. I understood you. And in addition.
I continued the installation and got a little further, but got stuck again. If you don't mind, I'll ask questions here so I don't have to create a new ticket. But if you say, I will create a new ticket. So, the installation went well, I didn't notice any serious errors. Before that I installed all In istio-system CronJob The problem now is with the certificates. I'm not really sure if I need the Currently the pod can't start because of. Because of the same error And also
I can forward the gui, but I can't see anything there. Only Homepage. All other menu links don't work. And it crashes with the same error. I attach a screenshot. But if I forward ml-pipelines-ui separately, it seems to be working. I install kubeflow with these values.
Sorry for the trouble. Hope this helps someone in the future. |
Hi @kromanow94 . Are you still available for help or should I look for other ways to install. Thanks for the reply. |
Hey @JWebDev , sorry for the late reply. Just yesterday I got back from my holidays :). Thank you for all of the details. I'm happy you were able to move forward with the issue. In this scenario, do you install cert-manager at all? Is it healthy? In the past I noticed such errors when there were issues with the cert-manager. It doesn't have to be configured with any provider like Lets Encrypt but it has to exist and be healthy on the cluster because Kubeflow relies on a few self-signed certificates it uses mostly for Admission Webhooks. The cert-manager is used to provide a few certificates for the Admission Webhooks, and those are using self-signed certificates. For example:
The Having that in mind, are you using any of the quickstarts scripts available under About the Let me know if that helps and if you have any other issues. |
Hi @kromanow94 Glad to hear from you. Hope you had a good vacation. ))) I looked at the error again after my post and realized that I was missing kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-workflows/refs/heads/main/manifests/base/crds/minimal/argoproj.io_clusterworkflowtemplates.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-workflows/refs/heads/main/manifests/base/crds/minimal/argoproj.io_cronworkflows.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-workflows/refs/heads/main/manifests/base/crds/minimal/argoproj.io_workflows.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-workflows/refs/heads/main/manifests/base/crds/minimal/argoproj.io_workflowtemplates.yaml May be useful to someone. Is this enough or do I need to install Argo Workflows and somehow specify Kubeflow installation method? I would be grateful if you could clarify this point. Regarding your question. Yes, I have cert-manager installed. And as I described above - it seems to have solved the problem with certificates. The same problem remains with I just need Maybe you know how I can get around this? Thanks for the help! |
Thank you, I really enjoyed my holiday :). About the Argo Workflows, yes, the full installation is required. This is because Argo Workflows is used as a backend and when the Kubeflow Pipeline Run is created, an Argo Workflow Object is created on the cluster. I agree that this information is not emphasized enough. On the default kubeflow installation that you get from the kustomize in Some of the information on Argo WF requirement you can find here: The full installation reference for this Helm Chart with all the dependencies, their values and ordering can be see under the link below. You issue with accessing the cluster seems familiar. If you were to use any of the quickstart scripts (like the service:
type: ClusterIP With the above, it should be just enough to execute the following to make kubeflow available through the
If you were to use the quickstart, you'd also see that M2M connectivity is also enabled and configured by default:
|
@kromanow94 Thaaaaanks. Where were you with this script before? ))) Ok, I think I understand with I looked at the script. Everything is more or less clear, as I have already understood a lot of things during my installation research. It seems to be one of the most complicated installations I've done.
Please add in Readme that there are these scripts. I didn't notice something about them. Thanks again! |
Finally I went step by step through the whole script. Well structured. Thanks. Got the istio-ingressgateway forwarding. The dex authorization page appeared. Authorized with my user. The kubeflow dashboard was displayed. But unfortunately some problems with the certificate. I don't know what to look for and where to look, as the logs showing no error in kubeflow or istio namespaces and everything is correct.
Almost all pages do not load with this error. I'm attaching a screenshot. I have changed the username everywhere to 'kubeflow-user'. Also 'Endpoints' shows The pages that display correctly are. 'Home', 'Experiments' and 'Manage Contributors'. On 'Experiments' I can select all steps and so on. I mean the page is fully working. Any idea how I can fix these errors? |
I agree, the information about quickstart scripts could be made more clear. I think it makes sense to include that as part of the #14. Yes, this installation works with the MySQL used in the quickstarts. It was tested by a numer of people, number of times, without issues. FYI, this is the mysql image in bitnami/mysql Helm Chart:
Metacontroller is used for Your error with metacontroller seems to be caused by the extra dot in the "
Please double check if you did any change accidentally in the CompositeController for For the As for the issue with displaying the Central Dashboard and the pages for Pipelines and Models, I don't know where the issue is. What I can suggest is to start with a fresh install using clean git-tree for |
Thanks for the quick reply. Oh, for some reason I thought the version “9.21.2” was the version of image. Now I see what version it is in mysql. Metacontroller - understood CompositeController - no, I didn't make any changes there at all. I installed selectively and with my values. For example, I do not use MinIO because I have Ceph. And I copied all the values and changed them to my own values. So just checkout will not help me unfortunately. But I can't check after each installation what exactly is broken, because to start everything I need to install almost all components. Ok, I will try to find and understand the error. Thanks. If you have any more ideas, please write me. |
If something comes up to me, I'll let you know. Also, feel free to add more findings and please share the final resolution :). |
Hi. @kromanow94 I found a mistake! ))) Here's how to fix it. 3 more small things.
Thanks! |
Hi Krzysztof,
I'm trying to install Kubeflow on my Kubernetes cluster (Bare Metal).
I've been looking for helm charts for a long time and realized that they are almost non-existent. Stumbled upon your development and decided to give it a try.
But I have some difficulties, so I decided to ask a question/suggestion here, hopefully, you will take a look and be able to help me or at least answer.
The first thing I really didn't like, but I understand that no one has any influence on this as it is historically. It's a rigid tie-in to Istio.
I can understand the need to use Istio. But this is very limited thinking for the future, as not everyone needs it and not everyone supports Istio.
I am installing step by step, not including all components to start with, only Dashboard and Pipelines so far.
The first problem I encountered is the inability to start “ml-pipeline-metadata-grpc-server” with this error.
I'm ruling out the possibility of lack of communication or rights, since I'm passing the root user rights and the connectin exists.
Most likely the problem is in the “MySQL authentication plugin” as I am using MySQL 8 and the mysql_native_password plugin is disabled there.
Is there any way to customize this parameter in “ml-pipeline-metadata-grpc-server” or is it impossible?
My second question concerns istio-gateway and certificates.
I've already accepted that I can't start Kubeflow without it and will install all the necessary components. But is it possible to somehow configure that I don't need to assign a certificate via certificate-manager?
I don't have a public installation and I don't want to expose Kubeflow to the outside to protect it later. But the way it's done there, you can't start istio-gateway without a certificate and for that you have to assign a domain and get a LetsEncrypt certificate and so on, which is additional and unnecessary work.
I saw your comment that at the moment installation without certificate-manager is not possible.
What is the best way to get around this?
Thanks!
The text was updated successfully, but these errors were encountered: