This page describes the Kubeflow resources and support options that you can explore when you encounter a problem, have a question, or want to make a suggestion about Kubeflow.
Starting from the release of Kubeflow v1.0, the Kubeflow community attributes stable status to those applications and components that meet a defined level of stability, supportability, and upgradability.
When you deploy Kubeflow to a Kubernetes cluster, your deployment includes a number of applications. Application versioning is independent of Kubeflow versioning. An application moves to version 1.0 when the application meets certain criteria in terms of stability, upgradability, and the provision of services such as logging and monitoring.
When an application moves to version 1.0, the Kubeflow community will decide whether to mark that version of the application as stable in the next major or minor release of Kubeflow.
Application status indicators for Kubeflow:
- Stable means that the application complies with the criteria to reach application version 1.0, and that the Kubeflow community has deemed the application stable for this release of Kubeflow.
- Beta means that the application is working towards a version 1.0 release and its maintainers have communicated a timeline for satisfying the criteria for the stable status.
- Alpha means that the application is in the early phases of development and/or integration into Kubeflow.
Levels of support
The following table describes the level of support that you can expect based on the status of an application:
|Application status||Level of support|
|Stable||The Kubeflow community offers best-effort support for stable applications. See the section on community support below for a definition of best-effort support and the community channels where you can report and discuss the problem. You can also consider requesting support from a Kubeflow community provider or from your cloud provider.|
|Beta||The Kubeflow community offers best-effort support for beta applications. See the section on community support below for a definition of best-effort support and the community channels where you can report and discuss the problem.|
|Alpha||The response differs per application in alpha status, depending on the size of the community for that application and the current level of active development of the application.|
Support from the Kubeflow community
Kubeflow has an active and helpful community of users and contributors.
The Kubeflow community offers support on a best-effort basis for stable and beta applications. 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 the following are true:
- 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 of the problem can help with further diagnosis and troubleshooting.
You can ask questions and make suggestions in the following places:
Slack for online chat and messaging. See details of Kubeflow’s Slack workspace and channels.
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 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’re encountering and learn about any workarounds to date. If no one has logged your problem, create a new issue to describe the problem.
Each Kubeflow application has its own issue tracker within the Kubeflow organization on GitHub. To get you started, here are the primary issue trackers:
Support from providers in the Kubeflow ecosystem
The following organizations offer advice and support for Kubeflow deployments:
|Organization||Points of contact|
|Canonical||Get in touch|
|Patterson Consulting||Managed Kubeflow|
Support from a cloud or platform provider
If you’re using the services of a cloud provider to host Kubeflow, the cloud provider may be able to help you diagnose and solve a problem.
Consult the support page for the cloud service or platform that you’re using:
- Amazon Web Services (AWS)
- Canonical Ubuntu
- Google Cloud Platform (GCP)
- IBM Cloud
- Microsoft Azure
- Red Hat OpenShift
Other places to ask questions
You can also try searching for answers or asking a question on Stack Overflow. See the questions tagged with “kubeflow”.
Getting involved in the Kubeflow community
You can get involved with Kubeflow in many ways. For example, you can contribute to the Kubeflow code or documentation. You can join the community meetings to talk to maintainers about a specific topic. See the Kubeflow community page for further information.
Following the news
Keep up with Kubeflow news:
The Kubeflow blog is the primary channel for announcement of new releases, events, and technical walkthroughs.
Follow Kubeflow on Twitter for shared technical tips.
The release notes give details of the latest updates for each Kubeflow application.
Each Kubeflow application has its own repository within the Kubeflow organization on GitHub. Some of the applications publish release notes. To get you started, here are the release notes for the primary applications:
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.