search

f0cker / crackq

CrackQ: A Python Hashcat cracking queue system
MIT License
922 stars 101 forks source link

Kubernetes integration? #3

Open zoobab opened 4 years ago

zoobab commented 4 years ago

Hi,

Do you have some integration with Kubernetes?

Most of the design patterns could be solved by using GPUs on kubernetes worker nodes (with labels).

And kubernetes jobs could be spawned.

Just thinking loud here...

f0cker commented 4 years ago

No not at present, the easy cloud integration was really just a pleasant side-effect of the way the application was designed but it wasn't an intentional design goal. It's using docker-compose to manage the containers, but none of them are really resource intensive except for the Hashcat container which is within the same container as the REST API/WSGI. I'm not hugely familiar with Kubernetes, do you think there would be an advantage using that over docker-compose in this case? I've thrown a lot at it in testing and it's handled it well in its current state. I don't think it would be difficult to implement, would just need to port the docker-compose yml files over to Kubernetes format.

zoobab commented 4 years ago

" I don't think it would be difficult to implement, would just need to port the docker-compose yml files over to Kubernetes format."

I can try to five it a shot. Otherwise there is Kompose which converts docker-compose.yml to k8s.yml, but by hand it is probably the best.