change: UIE-10060 - Enable feature flag to show/hide blackwell GPU plans in LKE plans panel#13421
Closed
grevanak-akamai wants to merge 3 commits intolinode:release-v1.159.0from
Conversation
… accounts table (linode#13412) * fix + test * Added changeset: Empty message for `SwitchAccountDrawer` child accounts table * feedback @bnussman-akamai
…in LKE plans panel
grevanak-akamai
assigned
pmakode-akamai and
tanushree-akamai and unassigned
pmakode-akamai and
tanushree-akamai
…-flag-for-gpu-in-lke
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description 📝
Enable feature flag for GPU blackwell plans in LKE plans panel. This check was recent removed as part of PR to enable GPU plans in LKE flow for GA but this program is on hold for now. So we are adding back the feature flag check.
Changes 🔄
kubernetesPlansPanel.tsx, add a check to show/hide blackwell GPU plans based on feature flag.Scope 🚢
Upon production release, changes in this PR will be visible to:
Target release date 🗓️
Feb 2026
Preview 📷
How to test 🧪
Prerequisites
Verification steps
Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅