In Kubernetes most classes are reused in many places. A PodSpec for example is valid in a Pod, but also in a Deployment or StatefulSet. Same e.g. with Metadata.
The actual behaviour of creating and naming classes makes it impossible to reuse code that creates constructs like e.g. a PodSpec.
It would be nice if properties that reference the same class in Kubernetes also have the same classes in the generated code (Java) to make it easier to build and reuse custom constructs and functions.
class DeploymentV1 {
metadata: Metadata
}
class SecretV1 {
metadata: Metadata
}
References
No response
Help Wanted
[ ] I'm interested in contributing a fix myself
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
In Kubernetes most classes are reused in many places. A
PodSpecfor example is valid in aPod, but also in aDeploymentorStatefulSet. Same e.g. withMetadata.The actual behaviour of creating and naming classes makes it impossible to reuse code that creates constructs like e.g. a
PodSpec.It would be nice if properties that reference the same class in Kubernetes also have the same classes in the generated code (Java) to make it easier to build and reuse custom constructs and functions.
References
No response
Help Wanted
Community Note