[CNCF Insights] UX patterns from 2026-07-15

## CNCF Landscape Intelligence Report

**Scanned repos:** jaegertracing/jaeger-ui goharbor/harbor grafana/grafana kiali/kiali
**Period:** Last 7 days | **Frontend-relevant PRs found:** 56

### UX Theme Distribution

| Theme | Hits | Relevance to Console |
|-------|------|---------------------|
| Accessibility | 2 | ARIA labels, keyboard navigation, screen reader support |
| Navigation & Search | 8 | Sidebar navigation, deep linking, search/filter/sort |
| Responsive & Mobile | 1 | Mobile-friendly dashboard layouts, collapsible panels |
| Data Visualization | 7 | Charts, graphs, time series for metrics cards |
| Forms & Input | 24 | Cluster creation forms, config editors, validation |
| Real-time & Live Updates | 8 | SSE streams, live dashboard updates, auto-refresh |
| Onboarding & Guided Setup | 2 | First-run experience, setup wizards, empty state CTAs |
| Theming & Dark Mode | 7 | Theme switching, CSS variables, design tokens |

### What These Projects Are Doing (with context)

Each PR below includes its description so you can see *what* they changed and *why* — not just a title.

#### jaegertracing/jaeger-ui (1 frontend PRs)

- **[fix(stats): Make heatmap theme-aware](https://github.com/jaegertracing/jaeger-ui/pull/4200)**
  > ## Which problem is this PR solving? . Trace Statistics used hard-coded light RGB backgrounds for the `Color by` heatmap. In dark mode those backgrounds were paired with light theme text, making lower-intensity rows unreadable. ## Description of the 


#### goharbor/harbor (3 frontend PRs)

- **[cherry-pick: fix(ui): use dark login background in dark mode](https://github.com/goharbor/harbor/pull/23539)**
  > ## Fixes - [x] Addresses the login dark-mode background mismatch on the sign-in screen. Cherry-pick of #23535 - 

- **[docs: fix markdown formatting issues in CONTRIBUTING.md and README.md](https://github.com/goharbor/harbor/pull/23537)**
  > (no description)

- **[fix(ui): use dark login background in dark mode](https://github.com/goharbor/harbor/pull/23535)**
  > Thank you for contributing to Harbor! # Comprehensive Summary of your change Clarity's built-in login illustration uses a fixed light palette, so switching Harbor to dark mode only updated the login form and left the illustration bright. This change 


#### grafana/grafana (34 frontend PRs)

- **[IAM: Fix team member removal dual write response](https://github.com/grafana/grafana/pull/128413)**
  > <!-- Thank you for sending a pull request! Here are some tips: 1. If this is your first time, please read our contribution guide at https://github.com/grafana/grafana/blob/main/CONTRIBUTING.md 2. Ensure you include and run the appropriate tests as pa

- **[Dashboard Migration: Fix stack overflow in v16 when panel span exceeds grid width](https://github.com/grafana/grafana/pull/128410)**
  > ## What this PR does Fixes a stack overflow in the v14→v16 dashboard schema migration when a legacy row panel has a `span` greater than 12. ### Root cause For a `span` of, e.g., 24, the migration computes `panelWidth = floor(span) × widthFactor = 24 

- **[Visual refresh: adjust panel + input styles](https://github.com/grafana/grafana/pull/128409)**
  > <!-- Thank you for sending a pull request! Here are some tips: 1. If this is your first time, please read our contribution guide at https://github.com/grafana/grafana/blob/main/CONTRIBUTING.md 2. Ensure you include and run the appropriate tests as pa

- **[Pyroscope Datasource: Remove from core plugins](https://github.com/grafana/grafana/pull/128404)**
  > ## Summary - Remove Pyroscope Datasource core plugin implementation (Go backend + React frontend) — now served by the external `grafana-pyroscope-datasource` plugin - Remove Pyroscope Datasource from Wire DI, core plugin registry, test fixtures, and 

- **[Storage: type the search-fields map keys with LowerGroupResource](https://github.com/grafana/grafana/pull/128402)**
  > The three maps that drive search indexing — the search-fields provider, the selectable fields, and the expected per-kind hashes — were keyed by a lower-cased "group/resource" string built inline at every call site. This replaces that with a small `Lo

- **[LogsTable: use TableNG instead of TablePanel as integration point](https://github.com/grafana/grafana/pull/128401)**
  > Currently, the LogsTable panel component mounts the TablePanel root component. This is ok, but it does prevent us from doing proper panel decoupling between these two panels long-term. To me, it's worth having a bit of duplication between these two p


#### kiali/kiali (18 frontend PRs)

- **[Upgrade prettier, pretty-quick, and husky to latest major versions](https://github.com/kiali/kiali/pull/10056)**
  > Fixes the remaining part of #9708 (the ESLint portion was already handled in #9951/#9957). ## Summary - `prettier`: 2.0.5 → ^3.6.2 - `pretty-quick`: 2.0.1 → ^4.2.2 - `husky`: ^8.0.3 → ^9.1.7 - Updated `.husky/pre-commit`: removed the `husky.sh` sourc

- **[Remove refresh interval from Istio Config editor page](https://github.com/kiali/kiali/pull/10044)**
  > ### Describe the change The Istio Config details/editor page showed the global refresh interval dropdown and refresh button in the top-right toolbar, while a separate **Reload** button below the editor performed the same action. Auto-refresh is disru

- **[[v2.27] Show pod template annotations on workload detail page](https://github.com/kiali/kiali/pull/10040)**
  > ## Summary Backport of #10010 to v2.27. - Add sectioned annotation editor (controller vs pod template) for templated workloads - Add popover editor for viewing/editing large annotation values - Fix empty annotation value validation (empty strings are

- **[[2.27] fix perses url format in OpeShift](https://github.com/kiali/kiali/pull/10032)**
  > ### Describe the change Cherry pick from https://github.com/kiali/kiali/pull/10029 ### Steps to test the PR Recommendations for how to test this PR. Reminder that each PR should also include a "Test" label. ### Automation testing If applicable, expla

- **[CVE-2026-59869: Upgrade js-yaml to 4.3.0](https://github.com/kiali/kiali/pull/10031)**
  > Upgrade js-yaml from 4.1.0 to 4.3.0 to fix CVE-2026-59869, a Denial of Service vulnerability via crafted YAML documents using merge keys. Also update i18next-parser from 9.0.1 to 9.4.0 so its transitive js-yaml dependency uses a caret range instead o

- **[Update perses url format](https://github.com/kiali/kiali/pull/10029)**
  > ### Describe the change Update Perses link format for OpenShift ### Steps to test the PR Recommendations for how to test this PR. Reminder that each PR should also include a "Test" label. ### Automation testing If applicable, explain the case scencar


### Actionable Takeaways for KubeStellar Console

- **Accessibility** (2 PRs across repos) — CNCF projects are actively investing here. For our console: ARIA labels, keyboard navigation, screen reader support.
- **Navigation & Search** (8 PRs across repos) — CNCF projects are actively investing here. For our console: Sidebar navigation, deep linking, search/filter/sort.
- **Data Visualization** (7 PRs across repos) — CNCF projects are actively investing here. For our console: Charts, graphs, time series for metrics cards.
- **Forms & Input** (24 PRs across repos) — CNCF projects are actively investing here. For our console: Cluster creation forms, config editors, validation.
- **Real-time & Live Updates** (8 PRs across repos) — CNCF projects are actively investing here. For our console: SSE streams, live dashboard updates, auto-refresh.
- **Onboarding & Guided Setup** (2 PRs across repos) — CNCF projects are actively investing here. For our console: First-run experience, setup wizards, empty state CTAs.
- **Theming & Dark Mode** (7 PRs across repos) — CNCF projects are actively investing here. For our console: Theme switching, CSS variables, design tokens.

---
*Auto-generated by auto-qa-tuner CNCF intelligence scan*

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CNCF Insights] UX patterns from 2026-07-15 #44

CNCF Landscape Intelligence Report

UX Theme Distribution

What These Projects Are Doing (with context)

jaegertracing/jaeger-ui (1 frontend PRs)

Which problem is this PR solving? . Trace Statistics used hard-coded light RGB backgrounds for the `Color by` heatmap. In dark mode those backgrounds were paired with light theme text, making lower-intensity rows unreadable. ## Description of the

goharbor/harbor (3 frontend PRs)

Fixes - [x] Addresses the login dark-mode background mismatch on the sign-in screen. Cherry-pick of #23535 -

grafana/grafana (34 frontend PRs)

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Theme	Hits	Relevance to Console
Accessibility	2	ARIA labels, keyboard navigation, screen reader support
Navigation & Search	8	Sidebar navigation, deep linking, search/filter/sort
Responsive & Mobile	1	Mobile-friendly dashboard layouts, collapsible panels
Data Visualization	7	Charts, graphs, time series for metrics cards
Forms & Input	24	Cluster creation forms, config editors, validation
Real-time & Live Updates	8	SSE streams, live dashboard updates, auto-refresh
Onboarding & Guided Setup	2	First-run experience, setup wizards, empty state CTAs
Theming & Dark Mode	7	Theme switching, CSS variables, design tokens

[CNCF Insights] UX patterns from 2026-07-15 #44

Description

CNCF Landscape Intelligence Report

UX Theme Distribution

What These Projects Are Doing (with context)

jaegertracing/jaeger-ui (1 frontend PRs)

Which problem is this PR solving? . Trace Statistics used hard-coded light RGB backgrounds for the Color by heatmap. In dark mode those backgrounds were paired with light theme text, making lower-intensity rows unreadable. ## Description of the

goharbor/harbor (3 frontend PRs)

Fixes - [x] Addresses the login dark-mode background mismatch on the sign-in screen. Cherry-pick of #23535 -

grafana/grafana (34 frontend PRs)

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions

Which problem is this PR solving? . Trace Statistics used hard-coded light RGB backgrounds for the `Color by` heatmap. In dark mode those backgrounds were paired with light theme text, making lower-intensity rows unreadable. ## Description of the