Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly manage default or admission-controlled fields #38

Open
Tracked by #39
davidfestal opened this issue Mar 8, 2023 · 2 comments
Open
Tracked by #39

Correctly manage default or admission-controlled fields #38

davidfestal opened this issue Mar 8, 2023 · 2 comments

Comments

@davidfestal
Copy link
Member

davidfestal commented Mar 8, 2023

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
Copy link
Contributor

/transfer-issue contrib-tmc

1 similar comment
@mjudeikis
Copy link
Contributor

/transfer-issue contrib-tmc

@kcp-ci-bot kcp-ci-bot transferred this issue from kcp-dev/kcp Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next
Development

No branches or pull requests

2 participants