Protocol Buffer support needs automation to keep it in sync. #4367
Description
Describe the bug
The generated protobuf specification is inconsistent with the non protobuf classes.
The resources field is missing from the
V1.PodSpec.newBuilder()
.addResource(...) //missing
class V1PodSpec{
@SerializedName("resources")
@Nullable
private V1ResourceRequirements resources;
}
original golang specification
// +featureGate=PodLevelResources
// +optional
Resources *ResourceRequirements `json:"resources,omitempty" protobuf:"bytes,40,opt,name=resources"`
To Reproduce
Observe the generated protobuf code
https://github.com/kubernetes-client/java/raw/refs/tags/v25.0.0/proto/src/main/java/io/kubernetes/client/proto/V1.java
vs
Expected behavior
The resource shall be present in the protobuf variant too