swarm-cronjob VS tilt-extensions

Anything from simple crontab entry to something like this: https://crazymax.dev/swarm-cronjob/

So, I found a really nice little tool that solves a problem I have in a really nice way. Specifically, cron jobs on Docker Swarm. This project: https://github.com/crazy-max/swarm-cronjob It uses labels on your services to schedule jobs. Thus it needs access to the docker api, and all the security concerns that go along with it...

As i said, if it's not exposed to the outside world and doesn't work with untrusted data, that claim is not entirely valid.

Imagine something like this getting abandoned, or someone running a year old version of it: https://github.com/crazy-max/swarm-cronjob/blob/master/READM...

Its only job is to run containers on a particular schedule, no more no less. There are very few attack vectors for something like that, considering that it doesn't talk to the outside world, nor processes any user input data.

Then again, it's not my job to pass judgement on situations like that, merely acknowledge that they exist and therefore the consequences of those suddenly breaking cannot be ignored.

I also found swarm-cronjob and ofelia both seems promising. BUT , I really like the idea of an interface to watch log files etc.

The first is the load function which loads Tilt extensions. It's a way to expand the tool's features, and several are available. Here we are using docker_build_with_restart, which will update the container running inside our Kubernetes cluster.

This is the central viewport into manual resource control and environment enhancement through the open-source extensions for Tilt.

argocd for cd Tilt

Recently, I found Tilt [0] to be a good partner of mine to run "all services locally". It can be compared to "webpack (live-reloading, a lot of configuration possibilities) for backend". You want to run a bunch of services directly? Use local_resource()/local(). You have Procfile? There is procfile() function. You have docker-compose.yml with databases? You can run it too with docker_compose(). You want have Tiltfile and include them all-together? There is load(). You need some web-ui for frontend devs and a nice log browser? It is there too. You need to do some extra steps before running a service? You want to update your local cluster with newly built image on file save? No problem, tilt will do that with k8s_yaml() function. Tilt uses Titlfiles for configuration, which are written Pythonish Starlark language and you use them to run any specific logic there.

Also, I am not very lucky in having resemble 1:1 k8s cluster locally. You could be close but as long as you don't run already in cloud you will have different configuration (additional annotations, various quirks that do not exist in kind/k3s but they are on GCP). However, making dedicated dev environments in the cloud might be very costly and incur a lot of additional tinkering.

[0]: https://tilt.dev/

If `host` means your production/staging hosts or whatever, you should get out of that habit now. Look into something like tilt.dev or telepresence.io or any number of other solutions that help solve this issue. Doing it directly on any host is just a recipe for bad habits and disaster.

The article doesn't mention k3d (https://k3d.io/) which is a variant of k3s that runs in docker (rather than a VM) - very nice for k8s dev/test on developer workstations.

It integrates very nicely with https://tilt.dev/ also (another very useful tool for k8s related dev/test).

If this is an issue during development then you can use something like tilt with docker-compose to directly copy modified source inside container and incrementally build it. https://tilt.dev/

I'd add Tilt

Tilt

Along similar lines, how about comparing Devspace to [Tilt](https://tilt.dev/)?