You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users get confused and end up having to read through GitHub issues to know how to resolve the failure.
Proposal
The UI should detect when "metadata.annotations: Too long" is present in a Sync error message and present something like this:
This error usually means that you are applying a very large resource with client-side apply. Consider switching to Server-Side Apply or syncing with Replace enabled. Note that syncing with Replace enabled is potentially destructive, because it may cause resource deletion and re-creation.
The text was updated successfully, but these errors were encountered:
Summary
When a resource gets too big with client-side apply, users get an obscure error message: "metadata.annotations: Too long".
We know basically how the user should fix this: either replace the resource (if that's deemed safe) or use ServerSideApply.
Motivation
Users get confused and end up having to read through GitHub issues to know how to resolve the failure.
Proposal
The UI should detect when
"metadata.annotations: Too long"
is present in a Sync error message and present something like this:The text was updated successfully, but these errors were encountered: