Skip to content

feat: add cluster routing to raw-schema API with RBAC support - #260

Merged
iAlexeze merged 2 commits into
mainfrom
feature/raw-schema-remote-clusters
Aug 15, 2026
Merged

feat: add cluster routing to raw-schema API with RBAC support#260
iAlexeze merged 2 commits into
mainfrom
feature/raw-schema-remote-clusters

Conversation

@iAlexeze

@iAlexeze iAlexeze commented Aug 15, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add ?cluster=<name> parameter to /api/v1/raw-schema endpoint
  • Enable targeting remote clusters via gateway.clusters registry
  • Simplify handler signature to accept (kubeclient, cluster registry, katalog)
  • Generate RBAC rules per cluster for CRD schema access
  • Add resource checker to use TTL-based caching (30s)
  • Update RBAC generator rule to accommodate raw schema GET and LIST.

This PR also adds initial setup for an experimental feature: per target operatorBox.
The question is: Now that the Gateway is able to give multiple entry points to a CRD through targets and routable to multiple clusters, what can the runtime do with it? .

- Add ?cluster=<name> parameter to /api/v1/raw-schema endpoint
- Enable targeting remote clusters via gateway.clusters registry
- Simplify handler signature to accept (kubeclient, cluster registry, katalog)
- Add CRD get/list RBAC rules for gateway cluster permissions
- Generate RBAC rules per cluster for CRD schema access
- Fix resource checker to use TTL-based caching (30s)
- Fix RBAC rule generation to avoid cross-CRD rule contamination
@iAlexeze
iAlexeze merged commit b30aa25 into main Aug 15, 2026
8 checks passed
@iAlexeze
iAlexeze deleted the feature/raw-schema-remote-clusters branch August 19, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant