Add x-kubernetes-preserve-unknown-field to a CRD

[lburgazzoli]

I have a CRD where I need to include some unspecified fields, and I come up with something like:

class MySpec {
    String foo;
    Map<String, JsonNode> additionalProperties;
    
    @JsonProperty
    public void setFoo(String foo) {...}
    @JsonProperty
    public void getFoo() {...}
          
    @JsonAnySetter
    public void setAdditionalProperty(String key, JsonNode value) {...}

    @JsonAnyGetter
    public Map<String, JsonNode> getAdditionalProperties() {...}
}

However, as the generated CRD yaml, does not specify x-kubernetes-preserve-unknown-field, all unspecified fields are pruned so i.e. when I'm dogin kubectl get myresource, the only field that it is shown is foo.

Is there a way to declare that x-kubernetes-preserve-unknown-field should be set ?

[metacosm]

Not at this point. One thing to note, though, additionalProperties is supposed to be mutually exclusive with the properties field in the CRD JSONSchema so I'm not sure how that would work out. I've created a fabric8 client ticket, which is where this would be dealt with.

[andreaTP]

This feature have been actually implemented in the kubernetes-client:

fabric8io/kubernetes-client#3684
fabric8io/kubernetes-client#3691

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[andreaTP]

This issue is fixed since everything got merged in kubernetes-client and JOSDK updated it. cc. @csviri

[metacosm]

Thanks for confirming, @andreaTP!