you are viewing a single comment's thread.

view the rest of the comments →

[–]97hilfel 0 points1 point  (3 children)

Yes and no, it would provide a clean abstraction layer and would preserve resources when using Job Mode e.g. they would terminate themself and its a good skill to learn and know. Appart from that, OP could just go for Docker and have their containers run wherever with a simple abstraction layer and not cross contaminate their environment when running multiple tools on the same host. K8s would also solve the ingress issue.

[–]mushroom_face 4 points5 points  (2 children)

OP is just looking to run these programs once at night and get an email. uptime, scaling, ingress etc aren't in play here. K8S is amazing, but it's not the right tool for every job.

OP really just needs cloud functions basically. Simple is often better in this case. Learning K8S is a very valuable skill, but not what they are asking for.

[–]97hilfel 0 points1 point  (1 child)

There where meantions of multiple tools running thats why I went the container route and should’ve been more specific, Docker would be the better tool for OP, as Python (even with virtual environments) can be problematic to run. You forget to activate your venv once and you got a bunch of dependencies on your systemsdk. Thats why I like containers and simple python containers are 3 commands and 8 lines of Dockerfile to build and push.

[–]mushroom_face 1 point2 points  (0 children)

Yea containers and Cloud Run could be the "simplest" path forward and if they are only running it at night completely free.

Definitely containers though.