-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP-2906: Update Catalog schema for CRD compatibility #3220
Conversation
I think this looks good. I approve, but I'll drop a hold because I think my approval will auto merge it based on my enhancements role. And other reviewer, if you approve feel free to drop the hold /lgtm /hold for others to review |
@@ -743,30 +788,32 @@ definitions: | |||
type: array | |||
items: | |||
type: string | |||
KRMFunction: | |||
KRMFunctionDefinition: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to make the same changes to https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2985-public-krm-functions-registry, right? It leverages the KRMFunction
definition from here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will need to update it if we change the name here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call--the names.kind
change needs to be made there as well.
@@ -743,30 +788,32 @@ definitions: | |||
type: array | |||
items: | |||
type: string | |||
KRMFunction: | |||
KRMFunctionDefinition: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we want to change the name here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As part of strengthening the analogy to CRD, I though it would be useful to include "Definition" in the name of this type. In the same way that the CRD kind defines a CR rather than being one itself, this type defines a function. Does that make sense?
66d0596
to
2c96f05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: KnVerey, mengqiy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
Issue link: Kustomize KRM Plugin Catalog #2906
Comments: See fn framework: Enable validation using openAPI schema for functionConfig kubernetes-sigs/kustomize#4467 for an example use case. This really only required one change, i.e.
spec.kind
->spec.names.kind
. Here's the CRD reference, for reference. I also updated the type name for clarity (it's the CRD equivalent, not the CR). The rest of the updates are fixing examples that didn't match the schema even as it was before this PR./cc @mengqiy @jeremyrickard