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
Currently k8s_yaml(); only supports client-side apply.
Why Do You Want This?
Some some large yaml objects are impossible to apply using client-side apply.
Also it might be good for tilt to support server-side apply before it becomes default. They plan on making it the default.
Minor correction - k8s_yaml supports several different protocols for sending resources to the cluster, including a modified apply, a replace, and a delete+create, depending on what protocol makes the most sense. e.g., for large yaml objects it will usually use replace. cf #5065
(though agree that we should also add the ability to do server-side apply when the cluster supports it)
Describe the Feature You Want
Add optional support for server-side apply for k8s_yaml();
https://kubernetes.io/docs/reference/using-api/server-side-apply/
Current Behavior
Currently k8s_yaml(); only supports client-side apply.
Why Do You Want This?
Some some large yaml objects are impossible to apply using client-side apply.
Also it might be good for tilt to support server-side apply before it becomes default. They plan on making it the default.
Additional context
kubernetes/kubectl#712
banzaicloud/koperator#716
The text was updated successfully, but these errors were encountered: