Get Support

This page describes the Kubeflow resources and support options available when you encounter a problem, have a question, or want to make a suggestion about Kubeflow.

Component Status

Please make youself familiar with the structure of Kubeflow first. When you deploy Kubeflow to a Kubernetes cluster, your deployment includes multiple projects. Note that project versioning is independent from Kubeflow Platform version. Each project should meet certain criteria regarding stability, upgradability, logging, monitoring, and security (PodSecurityStandards restricted, network policies, and integration tests for authentication and authorization).

Component status indicators:

• Stable: The application complies with most of the criteria and is considered stable for this release.
• Beta: The application is progressing towards meeting most criteria.
• Alpha: The application is in an early development or integration stage.

Levels of Support

1. The Kubeflow community provides best-effort support for stable components.
2. You can also request commercial support from a company or freelancer listed below.

Support from the Kubeflow community

Kubeflow has an active and helpful community of users and contributors. The Kubeflow community provides support on a best-effort basis for stable and beta applications. If you need commercial support, please check the sections below.

Best-effort support means that there’s no formal agreement or commitment to solve a problem but the community appreciates the importance of addressing the problem as soon as possible. The community commits to helping you diagnose and address the problem if all of the following requirements are satisfied:

• The cause falls within the technical framework that Kubeflow controls. For example, the Kubeflow community may not be able to help if the problem is caused by a specific network configuration within your organization.
• Community members can reproduce the problem.
• The reporter can assist with troubleshooting.

You can ask questions and make suggestions in the following places:

• Slack for online chat and messaging, see Slack workspace and channels.

• GitHub discussions per repository, e.g. here

• Kubeflow discuss for email-based group discussion. Join the kubeflow-discuss group.

• Kubeflow documentation for overviews and how-to guides. In particular, refer to the following documents when troubleshooting a problem:

  • Kubeflow installation and setup
  • Kubeflow components

• Kubeflow issue trackers for known issues, questions, and feature requests. Search the open issues to see if someone else has already logged the problem that you are encountering and learn about any workarounds. If no one has logged your problem, create a new issue to describe the problem.

  Each Kubeflow component has its own issue tracker within the Kubeflow organization on GitHub. To get you started, here are the primary issue trackers:

  • Kubeflow Spark Operator
  • Kubeflow Pipelines
  • Kubeflow Katib
  • Kubeflow Trainer
  • Kubeflow Notebooks
  • Kubeflow Model Registry
  • Kubeflow Dashboard
  • Kubeflow Kserve
  • Kubeflow Platform / Manifests
  • Kubeflow Website

Support from commercial providers in the Kubeflow Ecosystem

We want to promote commercial companies and idividuals that contribute back to the open source project. Below is a table of organizations that contribute to Kubeflow and offer commercial support:

If you are using a managed offer from a cloud provider for Kubeflow, then the cloud provider may be able to help you diagnose and solve a problem.

Getting Involved

You can participate in Kubeflow by contributing funding, code, documentation, use cases or by joining community meetings. For more information, see the Kubeflow Community page.

Stay Updated

Keep up with Kubeflow news:

• The community page with Slack channels, regular meetings and other guidelines.
• The Kubeflow Blog for release announcements, events, and tutorials.
• Kubeflow on Twitter for technical tips.
• Release notes for detailed updates on each Kubeflow application.