Skip to content

Release Notes - Version 2.2.0

Release Date: July 21, 2026

🎉 Highlights

Version 2.2.0 completes the Okta SSO rollout to production, equipping all platform emails with AMD-branded templates and giving administrators a new team-enabled flag to toggle team access without deleting teams. Capacity reporting is corrected so broken GPU nodes no longer appear as available resources. The UI gains responsive table layouts across all entity list views, and Okta sign-up errors are now surfaced clearly on the sign-in page. The chatbot documentation and help pages also receive minor updates.

🚀 New features

🔐 Okta SSO in production

The Okta identity provider integration is now live in the production environment. A dedicated production deployment workflow was added alongside a fully configured Okta-enabled inventory, completing the multi-release effort to bring enterprise SSO to AAC. New user sign-ups via Okta are gated behind the USER_AACA_MANAGEMENT feature flag, ensuring the flow is only active in environments that support managed provisioning. Users who sign up through Okta's local-signup path are no longer redirected to the password expiry flow, and Okta-authenticated sessions bypass the password expiration check entirely.

🏳️ Team enabled flag

Administrators can now enable or disable individual teams using a new team-enabled flag. Teams that are disabled remain in the system but their access is suspended, giving admins finer control over team lifecycle without requiring deletion and recreation.

📱 Responsive tables

All major entity list tables — teams, queues, applications, and other core views — are now wrapped in horizontal scroll containers. Embedded and secondary tables were audited and migrated by feature area to ensure consistent responsive behaviour across the platform. Users on smaller screens or narrower browser windows no longer see table content overflow outside the viewport.

✉️ AMD-branded email templates

All outgoing platform emails — including invitations, welcome messages, and transactional notifications — now use AMD colors, logos, and a simplified HTML layout aligned with AMD brand standards. The welcome email was fully updated to reflect AMD Accelerator Cloud branding throughout.

🔧 Improvements

  • Accurate GPU capacity reporting — Broken accelerator nodes are excluded from free-capacity calculations, preventing the platform from over-reporting available GPU resources.
  • Performance for large tenants — The team detail endpoint was optimised to avoid full user-set scans for organisations with many users, substantially improving response times.
  • Form field limits aligned — Invitation, sign-up, edit-account, team, and email field limits in the UI were updated to match the expanded character limits enforced by the API.
  • Job wizard type safety — The wizard job review step is now wired to the typed JobCreateRequestApi, and submission mapping was consolidated with additional branch tests.
  • Team name contains filter — The team list now applies a server-side name contains filter, reducing data transfer on large team datasets.
  • Expanded invitation field lengths — Maximum field lengths for the POST /invitations/ endpoint were increased to match the wider values allowed by the Carbonara data source.

🐛 Bug fixes

  • Fixed APU resources being dropped from workload specifications when gres was not provided — APU-based jobs now submit correctly
  • Fixed expired Okta invitations not returning a clear error — they are now rejected with a 403 status under managed provisioning
  • Fixed apt 404 errors during package installation by cleaning the package cache before each install
  • Fixed Okta sign-up-not-allowed errors not appearing on the sign-in page — the 403 response is now displayed as a clear, actionable message to the user

🔒 Security

  • Third-party deprecation warnings removed — Outdated third-party code patterns that generated deprecation warnings were cleaned up from the API codebase

← Back to What's New | Previous Release (v2.1.0) → | Next Release (v2.3.0) →