Skip to content

Conversation

@makdeniss
Copy link
Contributor

@makdeniss makdeniss commented Dec 19, 2025

Core API group simplification: removed the custom "core" group. Core resources are now accessed directly by version (e.g., v1) for queries/mutations, and core subscription names are flattened to start with the version (e.g., v1_configmaps).

Change Log

  • 🔥 (breaking) Queries/Mutations: Path changed from core { v1 { ... } } to v1 { ... }. Update client queries accordingly.
  • 🔥 (breaking) Subscriptions: Renamed from core_v1_<resource> to v1_<resource> (e.g., core_v1_configmapsv1_configmaps).
  • Docs: Updated docs/breaking-changes.md, docs/configmap_queries.md, docs/pod_queries.md, docs/quickstart.md, and docs/subscriptions.md to reflect the new core paths and subscription names.
  • Tests: Adjusted standard Kubernetes tests to use the new core paths/names.

@makdeniss makdeniss self-assigned this Dec 19, 2025
@makdeniss makdeniss added the enhancement New feature or request label Dec 19, 2025
@makdeniss makdeniss linked an issue Dec 19, 2025 that may be closed by this pull request
@makdeniss makdeniss changed the title feat: removal of custom core group (#111) feat: removal of custom core group Dec 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gateway introduces custom "core" group for core Kubernetes types

2 participants