Use k8s namespaces

[netr0m]

This PR ensures that the CTF services are separated in their own namespace juicer, rather than using the default default.

Depends on #48
Depends on #49

[olavis]

Wow, such a huuuge PR!! From what I can tell, it looks good, many very nice changes! I'm not super confident in my review though, because of the size 😅 I couldn't tell if the branch lacks some rebasing, since as you mention, it is dependent on other issues? If so, PLEASE rebase before readying it for review next time, so I can stop wasting time reviewing double (funny that you actually mentioned this yourself in the contributing readme lol). Otherwise, it would be good anyway to split things up a little, this one certainly does more than just using k8s namespaces.. 🤗

[netr0m]

Wow, such a huuuge PR!! From what I can tell, it looks good, many very nice changes! I'm not super confident in my review though, because of the size 😅 I couldn't tell if the branch lacks some rebasing, since as you mention, it is dependent on other issues? If so, PLEASE rebase before readying it for review next time, so I can stop wasting time reviewing double (funny that you actually mentioned this yourself in the contributing readme lol). Otherwise, it would be good anyway to split things up a little, this one certainly does more than just using k8s namespaces.. 🤗

For sure! I based the following branches on the unmerged work in the branch refactor/make-cloud-agnostic, which made this and the previous branch/PR really noisy. I've merged the previous branches to main now, and rebased this one on top to make it more readable!

[markusrf]

Great work, @netr0m ! 🎉