I was able to configure the whole setup to run on a kubernetes cluster and i will push the files when done.
There is still one Problem i mess around and mybe @s3inlc can clear that out easy.
system:
the kubernetes runs the db and the backend
the backend was modyfied to run apache2 under port 8080 also the 000-default file was set to host *.8080 (kubernetes doesnt allow 80)
the db and backend has a service and the backend service is linked to ingress to make the backend accessable via the ingress url resved for that , that all works well !
but when i want to access the api it comes to a redirect to port 8080 and i get rejected
Ingress is not able to handle port 8080 !
cause ?
Server only allows api under port 8080 ?
why is the dashboard and all running fine with no redirect problems / port problems but the api ?
messed it up with setting 000-default host to *.8080 ?
but apache runs actually under 8080 and is then ingressed (kind of proxied) to port 80
possible fixes?
disable mod rewrite ?
override ingress v-host to bla:8080 ? (guess wont work)
is it possible to set api to listen to other ports ?
any ideas ? :)
if we got that i can send the config.yamls for all the setup on kubernetes
Version Information
latest
Hashcat
No response
Description
Hey there, thanks for the great project ! @s3inlc
I was able to configure the whole setup to run on a kubernetes cluster and i will push the files when done. There is still one Problem i mess around and mybe @s3inlc can clear that out easy.
system: the kubernetes runs the db and the backend the backend was modyfied to run apache2 under port 8080 also the 000-default file was set to host *.8080 (kubernetes doesnt allow 80) the db and backend has a service and the backend service is linked to ingress to make the backend accessable via the ingress url resved for that , that all works well ! but when i want to access the api it comes to a redirect to port 8080 and i get rejected
Ingress is not able to handle port 8080 !
cause ? Server only allows api under port 8080 ? why is the dashboard and all running fine with no redirect problems / port problems but the api ? messed it up with setting 000-default host to *.8080 ? but apache runs actually under 8080 and is then ingressed (kind of proxied) to port 80
possible fixes? disable mod rewrite ? override ingress v-host to bla:8080 ? (guess wont work) is it possible to set api to listen to other ports ? any ideas ? :)
if we got that i can send the config.yamls for all the setup on kubernetes