Skip to content

Releases: intel/intel-data-center-gpu-driver-for-openshift

v2.2.0

19 Mar 17:47
@chaitanya1731 chaitanya1731
v2.2.0
3382d2b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.2.0 Latest
Latest

General

The OOT driver container image for OpenShift 4.14.11 and above based on RHEL 9.2.

What’s New

  • Added Intel Data Center GPU Max Series support by integrating Firmware binaries
  • Published the certified Intel Data Center GPU driver container images for RHOCP 4.14 with corresponding latest RHCOS kernels. See Release Information.
  • docker: Add PVC FW binaries to driver container by @hershpa in #72
  • docker: Updated Dockerfile by @chaitanya1731 in #78
  • docker: Optimize driver container image size by @hershpa in #79
  • Docker: Updated base UBI minimal version to latest by @chaitanya1731 in #83
    (Readme updates are not added in the above list)

Known Issues

Full Changelog: v2.1.0...v2.2.0

Contributors

chaitanya1731 and hershpa
Assets 2
Loading

v2.1.0

01 Feb 18:47
@chaitanya1731 chaitanya1731
v2.1.0
4e4209c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.1.0

General

The OOT driver container image for OpenShift 4.14 based on RHEL 9.2.

What’s New

  • Published the certified Intel Data Center GPU driver container images for RHOCP 4.14 with corresponding latest RHCOS kernels. See Release Information.

Known Issues

Full Changelog: v2.0.0...v2.1.0

Assets 2
Loading

v2.0.0

08 Nov 23:43
@chaitanya1731 chaitanya1731
v2.0.0
1138aad
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.0

General

The OOT driver container image for OpenShift 4.13.10 and 4.13.11 based on RHEL 9.2.

What’s New

  • Published the certified Intel Data Center GPU driver container image for above mentioned RHOCP with RHCOS kernel 5.14.0-284.28.1.el9_2.x86_64. Refer link for detailed release information.
  • Intel® Platform Monitoring Technology (Intel® PMT) module is now integrated with Intel® Graphics Driver Backports for Linux* OS (i915), hence removed the separate building of Intel PMT.
  • Upgraded base image from ubi8/ubi-minimal (RHEL 8.6) to ubi9/ubi-minimal (RHEL 9.2) for packaging GPU driver container.
  • Remove firmware for Max series GPU since we only support Flex series GPU now.

Known Issues

Full Changelog: v1.1.0...v2.0.0

Assets 2
Loading

v1.1.0

31 Aug 22:02
@chaitanya1731 chaitanya1731
v1.1.0
69128ed
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.1.0

General

The OOT driver container image for OpenShift 4.12.26.

What’s New

Published the certified Intel Data Center GPU driver container image for RHOCP- 4.12.26 RHCOS kernel. Refer link for detailed release information.

Known Issues

Assets 2
Loading

v1.0.0

29 Jun 18:25
@chaitanya1731 chaitanya1731
v1.0.0
8691300
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.0.0

General

The Intel Data Center GPU Driver for OpenShift project focuses on the development, packaging, certification, and release of Intel® Data Center GPU driver container images for the Red Hat OpenShift Container Platform (RHOCP).

This is the first release to provide the OOT driver container image for OpenShift 4.12.6.

What’s New

  • Provides dockerfile for building and packaging Intel Data Center GPU Driver container image.

  • Publish the certified Intel Data Center GPU driver container image for RHOCP- 4.12.6 RHCOS kernel. Refer link for detailed release information.

Known Issues

  • #49 How to handle scenario where out-of-tree driver depends on in-tree driver(s).
Assets 2
Loading