Community
Slack
Join the official Kubeflow Slack with this invite link.
Tip
If the above invite has expired, please raise an issue on thekubeflow/website repo.
The Kubeflow Slack workspace has many channels, here are a few examples:
| Topic | Slack Channel |
|---|---|
| General Discussion | #general |
| Feature Requests | #feature-requests |
| Job Postings | #job-postings |
| Kubeflow - Pipelines | #kubeflow-pipelines |
| Kubeflow - Notebooks | #kubeflow-notebooks |
| Kubeflow - KFServing | #kubeflow-kfserving |
| Platform - AWS | #platform-aws |
| Platform - Azure | #platform-azure |
| Platform - GCP | #platform-gcp |
| Users - China | #users-china |
| Users - Korea | #users-korea |
| Users - Oceania | #users-oceania |
Mailing List
The official Kubeflow mailing list is a Google Group called kubeflow-discuss.
More detail about the Kubeflow mailing lists:
| Topic | Mailing List |
|---|---|
| General Discussion | kubeflow-discuss |
Weekly Community Call
The Kubeflow community holds a public call every Tuesday, alternating between US East/EMEA and US West/APAC friendly times.
Tip
Joining the kubeflow-discuss Google Group will automatically send a calendar invitation to your email address.More detail about the Kubeflow weekly community call:
| Description | Link |
|---|---|
| Meeting Notes | Google Doc |
| Call Recordings | YouTube Playlist |
| Community Calendar | Google Calendar and iCal file |
| Community Calendar Management | GitHub Repo |
Blog
The official Kubeflow blog is found here.
Tip
To contribute an article for the blog, please raise an issue on the kubeflow/community GitHub repo. Note that articles are managed on the kubeflow/blog GitHub repo.Kubeflow Trademark
The Kubeflow trademark and logos are registered trademarks of Google, please review the Kubeflow Brand Guidelines for more information.
Kubeflow Working Groups
The Kubeflow project has a number of Working Groups (WGs) who each maintain some aspect of the Kubeflow project.
Feedback
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.