feat(kuadrant): read-only Gateway detail view (#369)

[R-Lawton]

Summary

Read-only detail view for the Gateway (gateway.networking.k8s.io/v1) resource, at /kuadrant/gateways/:namespace/:name. You land on it by clicking a Gateway row in the MCP overview table (#355). Closes #369.

What's here

Details tab — Name, Namespace, Ready/Status, Age, Labels, Annotations, Created at, Owner, and a Conditions table (Type, Status, Updated, Reason, Message).

YAML tab — the raw manifest, read-only, rendered with core-components CodeSnippet.

Changes

• Backend: GET /gateways/:namespace/:name returns the full Gateway manifest (mirrors the existing /httproutes/:namespace/:name handler).
• Frontend: kuadrantApi.getGateway(), the detail page, and the MCP Gateways table Name column now links to it.
• Gateway manifest types centralised in types/mcp.ts.

Testing

• Unit: GatewayDetailPage/utils.test.ts (14) + backend router.test.ts gateway-read cases (200/403/500).
• E2E: kuadrant-gateway-detail.spec.ts clicks through from the MCP Gateways table and checks the breadcrumb, Details tab, and YAML tab.
• yarn tsc and the above unit tests pass locally.

Definition of done

• Unit tests
• E2E tests (Playwright)
• Documentation updated (docs/ui-patterns.md)

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 714d5e0d-b563-42e2-82c6-2c96739926c3

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[R-Lawton]

Rebasing of main now that other resources have been added. Will match their style and use their existing code

[emmaaroche]

Two small consistency nits with the other two detail pages (McpGatewayExtensionDetailPage, McpServerRegistrationDetailPage):

• The Age field was dropped from both of those pages since Created At already covers it. Might be worth removing here too so all three detail pages stay aligned:

  kuadrant-backstage-plugin/plugins/kuadrant/src/components/GatewayDetailPage/GatewayDetailPage.tsx

  Lines 230 to 236 in eed5eda

  	<Box className={classes.infoItem}>
  	<Typography variant='caption' className={classes.label}>
  	Age
  	</Typography>
  	<Typography variant='body2'>
  	{formatAge(createdAt)}
  	</Typography>

• Owner is always shown here (falling back to - via getGatewayOwner), whereas the other two pages hide the Owner box entirely when there's no ownerReferences entry. Worth matching that pattern too:

  kuadrant-backstage-plugin/plugins/kuadrant/src/components/GatewayDetailPage/GatewayDetailPage.tsx

  Lines 238 to 243 in eed5eda

  	<Box className={classes.infoItem}>
  	<Typography variant='caption' className={classes.label}>
  	Owner
  	</Typography>
  	<Typography variant='body2'>{owner}</Typography>
  	</Box>

Both nits, not blocking - approving as is.

[emmaaroche]

Sorry, this will also need rebase 🙈

[Anton-Fil]

not rebase yet ?

[emmaaroche]

LGTM