Repository navigation
[BUG] Unable to validate certificates using ray plugin #4666
Description
Describe the bug
failed to load plugin - ray: [PluginInitializationFailed] Error getting informer for %!s(\u003cnil\u003e), caused by: failed to get API group resources: unable to retrieve the complete list of server APIs: ray.io/v1alpha1: Get \"https://X.X.X.X/apis/ray.io/v1alpha1\": x509: certificate signed by unknown authority
Unable to initialize the ray plugin because of a problem validating the certificate even with the caCertificate configured.
Expected behavior
Be able to validate the certificate using the caCertificate provided by the config.
Additional context to reproduce
Update to the last flyte version v1.10.6
Screenshots
No response
Are you sure this issue hasn't been raised already?
- Yes
Have you read the Code of Conduct?
- Yes
Activity
[-][BUG] [/-][+][BUG] Unable to validate certificates using ray plugin[/+]dosubot commentedon Jan 3, 2024
🤖
Hello @andresgomezfrr!
I'm Dosu, a friendly bot here to assist you while we wait for a human maintainer. I'm designed to help troubleshoot bugs, answer your questions, and guide you on becoming a better contributor.
Nice to meet you, and I'm ready to lend a hand with your issue!
Based on the error message you provided, it seems like there's an issue with the certificate validation when initializing the ray plugin. This could be due to a variety of reasons, such as incorrect certificate configuration or issues with the certificate authority.
I found a similar issue in the Flyte repository: [BUG] Wrong kubernetes client is used in plugin manager. The proposed solution was to use the correct Kubernetes client, as detailed in this pull request: Use correct k8 client. This might not be the exact solution to your problem, but it could potentially point you in the right direction.
Regarding the plugin initialization process in Flyte, it's handled by the
createRemotePluginfunction. This function is responsible for loading the plugin, validating its configuration, registering any custom states or resource quotas, creating a new resource cache, and finally returning aCorePlugin. You can find more details about this process in the flyteplugins/go/tasks/pluginmachinery/internal/webapi/core.go file.Unfortunately, I wasn't able to find specific changes made in the Flyte v1.10.6 milestone release that could affect the initialization of plugins or changes made in the ray plugin initialization process. It's possible that the answer may be available elsewhere or I could have missed it.
To help you further, could you please provide more details about your setup? Specifically, it would be helpful to know how you've configured the caCertificate and any other relevant settings. Additionally, could you please share the steps you took to update to Flyte v1.10.6? This information could help identify potential issues with the update process or configuration that might be causing this problem.
Sources
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.