Alex Crawford

One last request: Can you update the commit message and description to reflect that the only change is to allow compression on all file types (not, just remote). I'd leave...

@bgilbert I'll let you make the final call on this one. The only point of contention is that this breaks backward compatibility. I'm arguing that we should do it anyway...

@lucab Is the intention to yell at the user if the version doesn't exactly match or to accept multiple versions?

> CT is being vendored into things like Matchbox. Users presumably expect to upgrade Matchbox without breaking their configs, and they don't control what CT version is vendored in. It's...

> the etcd and flannel sections the user lacks enough control We should fix this instead.

> One thing to note is that this would result in users needing separate configs for each provider a user wishes to use, since coreos-metadata produces provider-specific environment variables. This...

The "Download" link appears to work (http://pastie.org/pastes/9250779/download). Looks like the docs just need to be tweeked.

The correct way to do this is to use Ignition to mask both locksmith and update engine. I realize that in your case, @cemo, you are unable to use Ignition.

It is not possible to downgrade. You can _rollback_, but that is just to the previously-installed version. What can we change in the wording to make this more clear?

In https://coreos.com/os/docs/latest/manual-rollbacks.html#performing-a-manual-rollback, we have the following: > ...we can tweak the process so that it boots an older image (assuming it's still intact on the passive partition). There isn't much...