Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Apply all resources in a single kubectl call #872
In an attempt to make full-syncs as fast as possible, this change combines all yamels into a big multidoc and attempts to apply that with a single kubectl call.
In the event that the mega-apply fails, fallback to applying yamels one at a time.
Obligatory random cleanups included at no extra cost.
Yes (to both), fallback yet to be implemented.
I'm trying to figure out if there's some way to get the best of both worlds (single
Does this make syncs appreciably faster? It's one exec vs ~100, of course, but I would expect most of the latency to be from the network round-trips kubectl does on each apply.
I'm also worried that there's much more chance of running into the limitation that caused #826 (which will be built into kubectl). It'd be quite easy to accumulate 64k of manifests. Granted, it will fall back to doing things one by one.