Skip to content
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

Define a scheme to use OpenAPI extension mechanisms for kpt functions #1505

Closed
natasha41575 opened this issue Mar 1, 2021 · 0 comments
Closed
Assignees
Labels
area/hydrate design-doc p1 triaged Issue has been triaged by adding an `area/` label

Comments

@natasha41575
Copy link
Contributor

natasha41575 commented Mar 1, 2021

From @mengqiy's document:

We need to augment OpenAPI with additional semantics to provide more metadata:

  1. The actual meaning of a field. I.e. field X in GVK Y is Z. e.g. Field .spec.selector in GVK core.v1.Service is a “label”.
  2. The linkage between objects. I.e. field X in GVK Y references field Z in GVK W. e.g. Field .spec.containers.envFrom.configMapRef.name references filed .metadata.name in core.v1.ConfigMap.

Task is to define the scheme for this

@natasha41575 natasha41575 self-assigned this Mar 1, 2021
@natasha41575 natasha41575 added this to To do in kpt kanban board via automation Mar 1, 2021
@natasha41575 natasha41575 moved this from To do to In progress in kpt kanban board Mar 1, 2021
@mikebz mikebz added area/fn-sdk Typescript SDK triaged Issue has been triaged by adding an `area/` label p1 labels Mar 1, 2021
@natasha41575 natasha41575 added area/openapi and removed area/fn-sdk Typescript SDK labels Mar 4, 2021
kpt kanban board automation moved this from In progress to Done Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/hydrate design-doc p1 triaged Issue has been triaged by adding an `area/` label
Projects
Development

No branches or pull requests

3 participants