Bitfusion with Kubernetes Integration

• bitfusion-with-kubernetes-integration is not required to run Bitfusion with Kubernetes.
• Kubernetes integration is included with Bitfusion.
• bitfusion-with-kubernetes-integration is community supported and is not supported by VMware Tech Support. If you have a problem open an issue on Github.

This project is a collection of tools for Bitfusion to be used with Kubernetes and Docker. For more information about Bitfusion, visit vSphere Bitfusion document page. This project contains:

• Bitfusion device plugin for Kubernetes
• Dockerfile templates for Bitfusion client
• Shell scripts to accelerate the deployment

Features

• Bitfusion device plugin provides the interface for applications to request Bitfusion GPU resources via Kubernetes native mechanism. Also, it could help to bake Bitfusion client image automatically.
• Dockerfile templates show Bitfusion client Docker image file samples, which could help to build customized Bitfusion application Docker images.
• Shell script is provided to build Bitfusion execution environment automatically.

Usage

• For device plugin, refer to this page for more usage information.
• Dockerfile templates are located in the directory ./Dockerfiles to set up a Bitfusion client based on different OS automatically. After deployment, you could run bitfusion smi command to check remote GPU resource of Bitfusion server connected to this Bitfusion client.
• nvidia-env.sh is a shell script to install needed various dependencies of Bitfusion client.

Feedback

Feel free to send us feedback by filing an issue. Feature requests are always welcome. If you wish to contribute, please take a quick look at the next section.

How to Contribute

This project team welcomes contributions from the community. If you wish to contribute code and you have not signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For any questions about the CLA process, please refer to our FAQ.

• Clone this repository and create a new branch.
• Make changes and test.
• Submit Pull Request with comprehensive description of changes.