manager: run kresctl from the executor's working directory

This updates poethepoet to version ^0.22.0, which allows tasks to have a working directory different from the project path.

This breaks the poe script on Python <3.8, but discussions took place on Slack where we came to the conclusion that this is fine. The script is meant for developers only and does not affect end users on systems that do not provide newer Python versions.

added manager label

requested review from @amrazek

CI currently seems to work fine even for Python 3.7, since our manager Dockerfile installed poethepoet explicitly, using a version that supported Python 3.7. Since only the kresctl task in pyproject.toml is incompatible with older versions of poethepoet, and the CI never uses kresctl, the tests pass as expected.

I'm thinking maybe we should update the Dockerfile to explicitly use python3.7 -m pip install poethepoet, so that we always have the 3.7-compatible version, even when we update the image?

added 1 commit

• 50d2dbde - ci/images/manager: ensure usage of Python 3.7

Compare with previous version

Added the change to Dockerfile. It's not yet uploaded to our GitLab registry, but I did local testing and it seems to work as expected.

added 1 commit

• 08259664 - manager/poe: allow python3.7 when executed from manager dir

Compare with previous version

added 1 commit

• 80871dad - manager/poe: allow kresctl to be run under Python <3.8

Compare with previous version

approved this merge request

added 16 commits

• 80871dad...cd103d95 - 12 commits from branch 6.0
• bd6eeb4e - manager: run kresctl from the executor's working directory
• e5601979 - ci/images/manager: ensure usage of Python 3.7
• 98c342fc - manager/poe: allow python3.7 when executed from manager dir
• 73fc67c7 - manager/poe: allow kresctl to be run under Python <3.8

Compare with previous version

merged

mentioned in commit 2e4244e4

I don't think the arm64 docker failure is related.

ERROR: failed to solve: debian:11-slim: failed to authorize: failed to fetch anonymous token: Get "https://auth.ipv6.docker.com/token?scope=repository%3Alibrary%2Fdebian%3Apull&service=registry.docker.io": dial tcp [2600:1f18:2148:bc00:e947:5a7f:a49f:9126]:443: connect: cannot assign requested address

Yea, looks to me like there is something wrong with the machine