Correctly manage default or admission-controlled fields

kcp-dev / contrib-tmc

An experimental add-on readding some Kubernetes compute APIs and impement transparent multi-cluster scheduling

Apache License 2.0

5 stars 3 forks source link

Correctly manage default or admission-controlled fields #38

Open davidfestal opened 1 year ago

davidfestal commented 1 year ago

When creating a resource in a KCP workspace, and this resource is Synced to the physical cluster, any field set during the creation of the resource on the physical cluster (default values or values set by the admission controllers) are not brought back to the KCP resource.

For example, a deployment created in a KCP workspace without specifying replicas, will end-up, when synced and started, as having 1/0 replicas.

mjudeikis commented 1 year ago

/transfer-issue contrib-tmc

mjudeikis commented 1 year ago

/transfer-issue contrib-tmc