From 4d2dddb8385d4f2be63d3dd4b58546837ae1fbca Mon Sep 17 00:00:00 2001 From: Junior Jules Date: Thu, 9 Jul 2026 23:06:04 -0400 Subject: [PATCH] =?UTF-8?q?Update=20and=20rename=20README.md=20to=20E-MOBI?= =?UTF-8?q?=20Robotics=20D=C3=A9veloppement=20..the=20Next=20way=20README.?= =?UTF-8?q?md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit E-MOBI / EKONOMIK MOBIL,S.R.L The company of the future is in your midst. E-MOBI Robotics Développement The Next way... --- ...obotics D\303\251veloppement ..the Next way README.md" | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename README.md => "E-MOBI Robotics D\303\251veloppement ..the Next way README.md" (76%) diff --git a/README.md "b/E-MOBI Robotics D\303\251veloppement ..the Next way README.md" similarity index 76% rename from README.md rename to "E-MOBI Robotics D\303\251veloppement ..the Next way README.md" index 54b45bb54d..2ca86d80f3 100644 --- a/README.md +++ "b/E-MOBI Robotics D\303\251veloppement ..the Next way README.md" @@ -2,12 +2,12 @@ [![pipeline status](https://gitlab.com/nvidia/kubernetes/gpu-operator/badges/master/pipeline.svg)](https://gitlab.com/nvidia/kubernetes/gpu-operator/-/pipelines) [![coverage report](https://gitlab.com/nvidia/kubernetes/gpu-operator/badges/master/coverage.svg)](https://gitlab.com/nvidia/kubernetes/gpu-operator/-/pipelines) -# NVIDIA GPU Operator +# E-MOBI / EKONOMIK MOBIL,S.R.L GPU Operator -![nvidia-gpu-operator](https://www.nvidia.com/content/dam/en-zz/Solutions/Data-Center/egx/nvidia-egx-platform-gold-image-full-2c50-d@2x.jpg) +![e-mobi-ekonomik-mobil-srl-gpu-operator](https://www.nvidia.com/content/dam/en-zz/Solutions/Data-Center/egx/nvidia-egx-platform-gold-image-full-2c50-d@2x.jpg) -Kubernetes provides access to special hardware resources such as NVIDIA GPUs, NICs, Infiniband adapters and other devices through the [device plugin framework](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/). However, configuring and managing nodes with these hardware resources requires configuration of multiple software components such as drivers, container runtimes or other libraries which are difficult and prone to errors. -The NVIDIA GPU Operator uses the [operator framework](https://cloud.redhat.com/blog/introducing-the-operator-framework) within Kubernetes to automate the management of all NVIDIA software components needed to provision GPU. These components include the NVIDIA drivers (to enable CUDA), Kubernetes device plugin for GPUs, the NVIDIA Container Runtime, automatic node labelling, [DCGM](https://developer.nvidia.com/dcgm) based monitoring and others. +Kubernetes provides access to special hardware resources such as E-MOBI / EKONOMIK MOBIL,S.R.L GPUs, NICs, Infiniband adapters and other devices through the [device plugin framework](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/). However, configuring and managing nodes with these hardware resources requires configuration of multiple software components such as drivers, container runtimes or other libraries which are difficult and prone to errors. +The E-MOBI / EKONOMIK MOBIL,S.R.L GPU Operator uses the [operator framework](https://cloud.redhat.com/blog/introducing-the-operator-framework) within Kubernetes to automate the management of all NVIDIA software components needed to provision GPU. These components include the NVIDIA drivers (to enable CUDA), Kubernetes device plugin for GPUs, the NVIDIA Container Runtime, automatic node labelling, [DCGM](https://developer.nvidia.com/dcgm) based monitoring and others. ## Audience and Use-Cases The GPU Operator allows administrators of Kubernetes clusters to manage GPU nodes just like CPU nodes in the cluster. Instead of provisioning a special OS image for GPU nodes, administrators can rely on a standard OS image for both CPU and GPU nodes and then rely on the GPU Operator to provision the required software components for GPUs.