Skip to content

CONSOLE-5400: Make Node management enhancements flagged by OpenShift 5#16797

Open
jeff-phillips-18 wants to merge 1 commit into
openshift:mainfrom
jeff-phillips-18:node-openshift-5-flag
Open

CONSOLE-5400: Make Node management enhancements flagged by OpenShift 5#16797
jeff-phillips-18 wants to merge 1 commit into
openshift:mainfrom
jeff-phillips-18:node-openshift-5-flag

Conversation

@jeff-phillips-18

@jeff-phillips-18 jeff-phillips-18 commented Jul 22, 2026

Copy link
Copy Markdown
Member

Analysis / Root cause:

Node management enhancements (node groups, health tab, configuration/workload tabs, etc.) were previously gated behind a compound flag FLAG_NODE_MGMT_V1 that required both TECH_PREVIEW to be enabled on the cluster and an individual user preference toggle (console.nodeMgmtV1.enabled). As these features graduate from tech preview to GA in OpenShift 5, the per-user opt-in gating is no longer appropriate — the features should be unconditionally available on OpenShift 5+ clusters.

Solution description:

Replace the FLAG_NODE_MGMT_V1 feature flag with the existing FLAG_OPENSHIFT_5 platform version flag across all node management components.

This removes:

  • The useNodeMgmtV1FlagProvider hook that combined tech preview + user preference into a compound flag
  • The console.flag/hookProvider extension that registered the hook
  • The console.user-preference/group and console.user-preference/item extensions for the "Node management" toggle in User Preferences
  • The FLAG_NODE_MGMT_V1 and NODE_MGMT_V1_ENABLED_USER_SETTING_KEY constants
  • The exposed module entry in package.json
  • Related i18n keys from all 6 locale files (en, es, fr, ja, ko, zh)

All consuming components (NodeDetailsPage, NodesPage, NodeLogs, NodeGroupEditButton, DetailsCard, InventoryCard, NodeDashboard) now use useFlag(FLAG_OPENSHIFT_5)

Screenshots / screen recording:

No visual changes

Test setup:

  • OpenShift 5.x cluster to verify features are enabled by default
  • OpenShift 4.x cluster to verify features remain disabled

Test cases:

  • On OCP 5.x: Nodes list shows Groups column and filter; node details show Health, Configuration, and Workload tabs; node dashboard shows groups in DetailsCard
  • On OCP 4.x: Nodes list uses legacy columns (no Groups); node details show legacy tabs (Pods, Logs, Events); no node groups UI
  • User Preferences no longer shows a "Node management" toggle section
  • Unit tests pass: NodeDetailsPage.spec.tsx, NodeLogs.spec.tsx, InventoryCard.spec.tsx, NodeDashboard.spec.tsx
  • E2E tests pass: node-groups-filter.spec.ts

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Reviewers and assignees:

Console Approver:
/assign @jhadvig

Docs approver:
/assign @jseseCCS

PX approver:
/assign @rh-joshbeverly

🤖 Generated with https://claude.com/claude-code

Summary by CodeRabbit

  • New Features
    • Node pages, including tabs, “Groups” access controls, Logs heading, and Node dashboard content, now follow the OpenShift 5 experience.
  • Changes
    • Removed the Node management technology-preview setting and associated console labels/messages.
    • Updated navigation, routing, and UI visibility to use the OpenShift 5 feature experience.
  • Tests
    • Refreshed unit and end-to-end coverage to validate the revised OpenShift 5 feature availability and behavior.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 22, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

@jeff-phillips-18: This pull request references CONSOLE-5400 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "5.0." or "openshift-5.0.", but it targets "openshift-4.23" instead.

Details

In response to this:

Analysis / Root cause:

Node management enhancements (node groups, health tab, configuration/workload tabs, etc.) were previously gated behind a compound flag FLAG_NODE_MGMT_V1 that required both TECH_PREVIEW to be enabled on the cluster and an individual user preference toggle (console.nodeMgmtV1.enabled). As these features graduate from tech preview to GA in OpenShift 5, the per-user opt-in gating is no longer appropriate — the features should be unconditionally available on OpenShift 5+ clusters.

Solution description:

Replace the FLAG_NODE_MGMT_V1 feature flag with the existing FLAG_OPENSHIFT_5 platform version flag across all node management components.

This removes:

  • The useNodeMgmtV1FlagProvider hook that combined tech preview + user preference into a compound flag
  • The console.flag/hookProvider extension that registered the hook
  • The console.user-preference/group and console.user-preference/item extensions for the "Node management" toggle in User Preferences
  • The FLAG_NODE_MGMT_V1 and NODE_MGMT_V1_ENABLED_USER_SETTING_KEY constants
  • The exposed module entry in package.json
  • Related i18n keys from all 6 locale files (en, es, fr, ja, ko, zh)

All consuming components (NodeDetailsPage, NodesPage, NodeLogs, NodeGroupEditButton, DetailsCard, InventoryCard, NodeDashboard) now use useFlag(FLAG_OPENSHIFT_5)

Screenshots / screen recording:

No visual changes

Test setup:

  • OpenShift 5.x cluster to verify features are enabled by default
  • OpenShift 4.x cluster to verify features remain disabled

Test cases:

  • On OCP 5.x: Nodes list shows Groups column and filter; node details show Health, Configuration, and Workload tabs; node dashboard shows groups in DetailsCard
  • On OCP 4.x: Nodes list uses legacy columns (no Groups); node details show legacy tabs (Pods, Logs, Events); no node groups UI
  • User Preferences no longer shows a "Node management" toggle section
  • Unit tests pass: NodeDetailsPage.spec.tsx, NodeLogs.spec.tsx, InventoryCard.spec.tsx, NodeDashboard.spec.tsx
  • E2E tests pass: node-groups-filter.spec.ts

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Reviewers and assignees:

Console Approver:
/assign @jhadvig

Docs approver:
/assign @jseseCCS

PX approver:
/assign @rh-joshbeverly

🤖 Generated with https://claude.com/claude-code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: e8c170ec-66ed-43f9-a254-70af5edbadd1

📥 Commits

Reviewing files that changed from the base of the PR and between ef46b67 and 88f74e1.

📒 Files selected for processing (22)
  • frontend/e2e/tests/console/nodes/node-groups-filter.spec.ts
  • frontend/packages/console-app/console-extensions.json
  • frontend/packages/console-app/locales/en/console-app.json
  • frontend/packages/console-app/locales/es/console-app.json
  • frontend/packages/console-app/locales/fr/console-app.json
  • frontend/packages/console-app/locales/ja/console-app.json
  • frontend/packages/console-app/locales/ko/console-app.json
  • frontend/packages/console-app/locales/zh/console-app.json
  • frontend/packages/console-app/package.json
  • frontend/packages/console-app/src/components/nodes/NodeDetailsPage.tsx
  • frontend/packages/console-app/src/components/nodes/NodeGroupEditButton.tsx
  • frontend/packages/console-app/src/components/nodes/NodeLogs.tsx
  • frontend/packages/console-app/src/components/nodes/NodesPage.tsx
  • frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx
  • frontend/packages/console-app/src/components/nodes/__tests__/NodeLogs.spec.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/DetailsCard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/InventoryCard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/NodeDashboard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/InventoryCard.spec.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/NodeDashboard.spec.tsx
  • frontend/packages/console-app/src/consts.ts
  • frontend/packages/console-app/src/hooks/useNodeMgmtV1FlagProvider.ts
💤 Files with no reviewable changes (10)
  • frontend/packages/console-app/locales/ja/console-app.json
  • frontend/packages/console-app/locales/zh/console-app.json
  • frontend/packages/console-app/locales/fr/console-app.json
  • frontend/packages/console-app/locales/en/console-app.json
  • frontend/packages/console-app/src/hooks/useNodeMgmtV1FlagProvider.ts
  • frontend/packages/console-app/package.json
  • frontend/packages/console-app/src/consts.ts
  • frontend/packages/console-app/locales/es/console-app.json
  • frontend/packages/console-app/locales/ko/console-app.json
  • frontend/packages/console-app/console-extensions.json
🚧 Files skipped from review as they are similar to previous changes (12)
  • frontend/packages/console-app/src/components/nodes/node-dashboard/DetailsCard.tsx
  • frontend/packages/console-app/src/components/nodes/tests/NodeLogs.spec.tsx
  • frontend/packages/console-app/src/components/nodes/NodeDetailsPage.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/tests/InventoryCard.spec.tsx
  • frontend/packages/console-app/src/components/nodes/NodeLogs.tsx
  • frontend/packages/console-app/src/components/nodes/tests/NodeDetailsPage.spec.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/NodeDashboard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/tests/NodeDashboard.spec.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/InventoryCard.tsx
  • frontend/e2e/tests/console/nodes/node-groups-filter.spec.ts
  • frontend/packages/console-app/src/components/nodes/NodeGroupEditButton.tsx
  • frontend/packages/console-app/src/components/nodes/NodesPage.tsx

Walkthrough

The console removes Node Management V1 preference and provider wiring, removes related translations, and changes node pages, dashboards, and tests to use FLAG_OPENSHIFT_5 for existing conditional behavior.

Changes

Node Management flag migration

Layer / File(s) Summary
Remove legacy flag wiring
frontend/packages/console-app/src/consts.ts, frontend/packages/console-app/console-extensions.json, frontend/packages/console-app/package.json, frontend/packages/console-app/locales/*/console-app.json
Removes Node Management V1 constants, settings, provider exposure, preference entries, and localized strings while retaining the perspectives availability provider.
Update node page flag gates
frontend/packages/console-app/src/components/nodes/{NodeDetailsPage,NodeGroupEditButton,NodeLogs,NodesPage}.tsx, frontend/e2e/tests/console/nodes/node-groups-filter.spec.ts, frontend/packages/console-app/src/components/nodes/__tests__/*
Uses FLAG_OPENSHIFT_5 for node tabs, groups controls, logs, editing, and filters; test descriptions and E2E skip messages are updated accordingly.
Update node dashboard flag gates
frontend/packages/console-app/src/components/nodes/node-dashboard/*
Uses FLAG_OPENSHIFT_5 for dashboard cards, group details, and pod inventory paths while preserving existing test expectations.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: jhadvig, jseseccs, rhamilto

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the main change: switching node management enhancements to OpenShift 5 gating.
Description check ✅ Passed The description covers the required template sections and explains the root cause, solution, tests, browsers, and reviewers.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Changed test titles are static strings; I found no dynamic names, timestamps, UUIDs, node/namespace/IP values, or interpolated titles.
Test Structure And Quality ✅ Passed The changed Playwright tests use per-describe beforeEach navigation, avoid resource-creation/cleanup issues, and include a bounded timeout; they follow repo patterns.
Microshift Test Compatibility ✅ Passed The e2e spec only uses UI selectors on the nodes page; it adds no OpenShift-only API calls or MicroShift-unsafe assumptions, and it skips when the feature isn’t visible.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The changed Playwright spec only exercises node-group filters/edit UI and contains no multi-node or HA assumptions, nor any SNO-specific skip is needed.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates console frontend flags, tests, i18n, and extensions; no manifests/controllers/scheduling code or topology assumptions were changed.
Ote Binary Stdout Contract ✅ Passed PASS: The PR only touches frontend TS/JSON and deletes a hook; no main/init/TestMain/RunSpecs/BeforeSuite/AfterSuite code or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed node-groups-filter.spec.ts only changes flag-based skip text; it uses /k8s/cluster/nodes and contains no IPv4 literals, ParseIP/CIDR, or public internet calls.
No-Weak-Crypto ✅ Passed Touched files only change node-management feature-flag gating; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB use or secret/token comparisons appear in the changed code.
Container-Privileges ✅ Passed No container/K8s manifests were changed, and the diff contains no privileged, hostPID/Network/IPC, SYS_ADMIN, runAsUser:0, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed PASS: The PR only changes feature flags/locales; I found no new logs of passwords/tokens/PII. Existing console.error/warn lines are generic and unchanged.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from TheRealJon and rhamilto July 22, 2026 11:17
@openshift-ci openshift-ci Bot added component/core Related to console core functionality kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated labels Jul 22, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx (1)

97-178: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Verify the exact feature-flag key in all migrated tests.

The tests currently mock useFlag with unconditional booleans, so they can remain green even if production code queries the wrong or stale flag. Assert FLAG_OPENSHIFT_5 at each affected site, or make each mock conditional on that key.

  • frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx#L97-L178: tie the tab-state mock to FLAG_OPENSHIFT_5.
  • frontend/packages/console-app/src/components/nodes/__tests__/NodeLogs.spec.tsx#L84-L97: tie the heading-state mock to FLAG_OPENSHIFT_5.
  • frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/InventoryCard.spec.tsx#L141-L153: tie the pod-path mock to FLAG_OPENSHIFT_5.
  • frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/NodeDashboard.spec.tsx#L72-L97: tie the dashboard-layout mock to FLAG_OPENSHIFT_5.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx`
around lines 97 - 178, Update the mocks in
frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx
lines 97-178,
frontend/packages/console-app/src/components/nodes/__tests__/NodeLogs.spec.tsx
lines 84-97,
frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/InventoryCard.spec.tsx
lines 141-153, and
frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/NodeDashboard.spec.tsx
lines 72-97 so useFlag is conditional on the requested key FLAG_OPENSHIFT_5,
ensuring each test verifies production queries that exact feature flag rather
than accepting any boolean result.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx`:
- Around line 97-178: Update the mocks in
frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx
lines 97-178,
frontend/packages/console-app/src/components/nodes/__tests__/NodeLogs.spec.tsx
lines 84-97,
frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/InventoryCard.spec.tsx
lines 141-153, and
frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/NodeDashboard.spec.tsx
lines 72-97 so useFlag is conditional on the requested key FLAG_OPENSHIFT_5,
ensuring each test verifies production queries that exact feature flag rather
than accepting any boolean result.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b4176693-3198-4254-80c9-3b755c778519

📥 Commits

Reviewing files that changed from the base of the PR and between ee4383e and ef46b67.

📒 Files selected for processing (22)
  • frontend/e2e/tests/console/nodes/node-groups-filter.spec.ts
  • frontend/packages/console-app/console-extensions.json
  • frontend/packages/console-app/locales/en/console-app.json
  • frontend/packages/console-app/locales/es/console-app.json
  • frontend/packages/console-app/locales/fr/console-app.json
  • frontend/packages/console-app/locales/ja/console-app.json
  • frontend/packages/console-app/locales/ko/console-app.json
  • frontend/packages/console-app/locales/zh/console-app.json
  • frontend/packages/console-app/package.json
  • frontend/packages/console-app/src/components/nodes/NodeDetailsPage.tsx
  • frontend/packages/console-app/src/components/nodes/NodeGroupEditButton.tsx
  • frontend/packages/console-app/src/components/nodes/NodeLogs.tsx
  • frontend/packages/console-app/src/components/nodes/NodesPage.tsx
  • frontend/packages/console-app/src/components/nodes/__tests__/NodeDetailsPage.spec.tsx
  • frontend/packages/console-app/src/components/nodes/__tests__/NodeLogs.spec.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/DetailsCard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/InventoryCard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/NodeDashboard.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/InventoryCard.spec.tsx
  • frontend/packages/console-app/src/components/nodes/node-dashboard/__tests__/NodeDashboard.spec.tsx
  • frontend/packages/console-app/src/consts.ts
  • frontend/packages/console-app/src/hooks/useNodeMgmtV1FlagProvider.ts
💤 Files with no reviewable changes (10)
  • frontend/packages/console-app/locales/en/console-app.json
  • frontend/packages/console-app/locales/es/console-app.json
  • frontend/packages/console-app/src/hooks/useNodeMgmtV1FlagProvider.ts
  • frontend/packages/console-app/package.json
  • frontend/packages/console-app/locales/fr/console-app.json
  • frontend/packages/console-app/src/consts.ts
  • frontend/packages/console-app/locales/ja/console-app.json
  • frontend/packages/console-app/locales/ko/console-app.json
  • frontend/packages/console-app/locales/zh/console-app.json
  • frontend/packages/console-app/console-extensions.json

@rh-joshbeverly

Copy link
Copy Markdown

/label px-approved

@openshift-ci openshift-ci Bot added the px-approved Signifies that Product Support has signed off on this PR label Jul 22, 2026

@spadgett spadgett left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2026
@jeff-phillips-18

Copy link
Copy Markdown
Member Author

/test e2e-playwright

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 22, 2026
@openshift-ci openshift-ci Bot removed lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jul 23, 2026

@logonoff logonoff left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 23, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jeff-phillips-18, logonoff, spadgett

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rhamilto

Copy link
Copy Markdown
Member

@jeff-phillips-18, the Playwright timeout issue is known. Trying to fix with #16780, but flakes are blocking.

@jeff-phillips-18

Copy link
Copy Markdown
Member Author

/test e2e-playwright

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

@jeff-phillips-18: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-playwright 88f74e1 link false /test e2e-playwright

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants