You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenAPI spec published by Kubernetes or by the cluster (kubectl get --raw /openapi/v2) lacks model for some types. These types are those used in webhooks, types for the representation of the .kube/config file, and types used in common extensions (metrics server, gateway-api, and so on).
To be able to generate the Java types using the new OpenAPI approach, we still need some mechanism to extract these specifications from the Go types and structs.
Specifications
Implement a new Go module in kubernetes-model-generator/openapi/generator: module github.com/fabric8io/kubernetes-client/kubernetes-model-generator/openapi/generator
Implement a CLI that accepts a single parameter to specify the output directory of the generated OpenAPI specs $ generator ./output
Generated APIs (more can be added later)
Name
Description
kubernetes-config.json
Types used in the Kubernetes configuration file (.kube/config)
api-machinery-extra.json
Additional types in apimachinery not directory exposed in swagger.json
Description
Part of #6130
The OpenAPI spec published by Kubernetes or by the cluster (
kubectl get --raw /openapi/v2
) lacks model for some types. These types are those used in webhooks, types for the representation of the.kube/config
file, and types used in common extensions (metrics server, gateway-api, and so on).To be able to generate the Java types using the new OpenAPI approach, we still need some mechanism to extract these specifications from the Go types and structs.
Specifications
kubernetes-model-generator/openapi/generator
:module github.com/fabric8io/kubernetes-client/kubernetes-model-generator/openapi/generator
$ generator ./output
kubernetes-config.json
.kube/config
)api-machinery-extra.json
swagger.json
admission-registration.json
gateway-api.json
kustomize.json
metrics-server.json
Implementation tasks and PRs
These are some of the bits that have already been implemented as part of the work done for #6080.
The text was updated successfully, but these errors were encountered: