William Walker

an old read, but `xar` might help with the CI/CD implementation of code signing for macOS and prevent the need for a Mac runner: https://users.wfu.edu/cottrell/productsign/productsign_linux.html

Inline with @RothAndrew's comment: > 1. Start with A, but do it in a way that the user is able to choose if they want HA or not. If I'm...

The PDB for the Zarf Registry requires a pod available at all times, but when a rolling node update takes place (for example upgrading EKS node AMIs), an additional registry...

Currently this isn't a supported option. IIRC, the way the `dyndns` configuration passes the ip and hostname URL query parameters is unique from other services. This would require significant rewrite/refactor,...

Fixed by #31

It is possible to bypass this issue by first stopping the container, _then_ pushing the update. The supervisor, under the **delete-then-download** strategy should do this rather than the user having...

Same error on supervisor ver 9.0.1 ``` 17.01.19 12:12:52 (-0500) Killing service 'main sha256:08251b0aa8d6c66bd1b240ea4cf172963e81cbd8bac252fb144ba7eaaa0b41a0' 17.01.19 12:12:52 (-0500) Deleting image 'registry2.balena-cloud.com/v2/0f74bea475cd7a34f257da6be491baa8@sha256:d8b60a410da5ab912d725ed19eba5624e71359814dc09f9f83b8b71ba77fc98f' 17.01.19 12:12:52 (-0500) Failed to delete image 'registry2.balena-cloud.com/v2/0f74bea475cd7a34f257da6be491baa8@sha256:d8b60a410da5ab912d725ed19eba5624e71359814dc09f9f83b8b71ba77fc98f' due to...

@CameronDiver thanks! If it helps at all, our current situation is: - Deploying a single container image (base image: balenalib/amd64-node:jessie) with a total payload of **955.08 MB** - Device Type:...

Any `SIGTERM` commands sent via the console, prior to initiating an update, are successful. Once the nightmarish update loop starts however, there's no response to any 'restart', 'stop' or 'start'...

@CameronDiver we can try the new supervisor image to test! How would we go about deploying the latest image to our machine?