kubectl --server-side apply replaces the live manifest instead of merging when migrating from clinet side apply to server side apply about kubernetes HOT 7 CLOSED

/sig api-machinery

from kubernetes.

/assign @alexzielenski @apelisse
/cc @jpbetz
/triage accepted

from kubernetes.

As outlined in the documentation (merge strategy and upgrading from client-side apply to server-side apply). According to my understanding, fields previously managed by client-side apply are expected to migrate to server-side apply. In cases where there's no other controller or manager managing these fields, they might be replaced by the new configuration applied via server-side apply.

If my understanding is correct, this behavior isn't a bug but rather an intended consequence of the transition process.

However, this migration behavior seems to be causing issues in ArgoCD after upgrading the Kubernetes and kubectl dependencies to v0.29.6, as discussed in ArgoCD issue #17882.
/help

from kubernetes.

@Mangaal:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

from kubernetes.

This is intended behavior of kubectl. It was a bug fixed relatively recently: #112905.

Mixing client-side-apply and server-side-apply is not supported. If you would like to manually manage a portion of your resource while ArgoCD manages another portion then please use SSA in your initial commands by adding --server-side=true and --field-manager=<DifferentFieldManager> for your manual application. If both manifests are applied using SSA and different field managers then they will complement each other as desired.

from kubernetes.

Thanks, @alexzielenski, for the confirmation.

from kubernetes.

Closing this issue

from kubernetes.