-
Notifications
You must be signed in to change notification settings - Fork 15.3k
List config API types explicitly #52658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This PR adds the "kinds" of resources exposed from various config APIs. Without this list, users may get confused why there are more than one versions of a given config API, and they may find it difficult to locate a specific "kind" of config API resource. With this embeded list of resource "kinds", users can easily understand that a given "kind" may have multiple versions and some "kinds" only exist in some group versions.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Pull request preview available for checking
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
@tengqm, this got overlooked. Would you be willing to rebase against main so we can see a preview relevant to the current docs? |
This PR is still up-to-date. No conflicts with |
This PR adds the "kinds" of resources exposed from various config APIs. Without this list, users may get confused why there are more than one versions of a given config API, and they may find it difficult to locate a specific "kind" of config API resource.
With these embedded lists of resource "kinds", users can easily understand that a given "kind" may have multiple versions and some "kinds" only exist in some group versions.
Description
Issue
Closes: #