Schnauzer templates instead of pluto

[tjkirch]

We migrated from pluto to schnauzer to generate pod-infra-container-image:

/// We moved from using pluto to schnauzer for generating the pause container image URL, since it
/// lets us reuse the existing region and arch settings, improving reliability and allowing for
/// testing new regions through settings overrides.

The same may well be true of other uses of pluto. In addition, it would be nice to have one less tool and to standardize on templated settings through schnauzer helpers.

This could help out-of-tree build efforts since we wouldn't need a tool like pluto to be specialized or understand any variant specifics; using schnauzer helpers instead means their use is determined by included settings and their templates.

[tjkirch]

Note: this may benefit from #1585 (dependencies between settings).

[zmrow]

I'm wondering about the "debug-ability" of having these types of things in template helpers. A service like pluto has the advantage of its output going directly to the journal. Template helpers don't have this luxury.

[tjkirch]

I'm wondering about the "debug-ability" of having these types of things in template helpers. A service like pluto has the advantage of its output going directly to the journal. Template helpers don't have this luxury.

If we fix:

bottlerocket/sources/api/apiserver/src/server/controller.rs

Line 477 in 452482a

// FIXME where to send output?

we should be able to get their logs.

[webern]

Closing as a historical relic that doesn't have a lot of bearing on Settings 2.0