Given we will have to upgrade the webtop often, we need to be able to easily adjust the requierd proxying in the wrongsecrets-balancer. That is why we need a configmap that contains a mapping for:
- which urls should end up to a websocket upgrade to which service
- which urls need to be proxied to which address
so, something like:
- websocket
- servicename1:8080:
incomingurl1
incomingurl2
incomingurl3
- serviname2:3000
incomingurl4
incomingurl5
- proxy
- servicename1:8080:
incomingurl6
incomingurl7
- servicename2:3000
incomingurl8withwildcard
- servicename3(CTFD)
incomingurl9
incomingurl10
- servicename4(grafana)
incomingurl10
the deployment should mount the configmap in so that the balancer its code should be able to read it. both the deployment and balancer code need to be adjusted.
https://github.com/OWASP/wrongsecrets-ctf-party/blob/main/wrongsecrets-balancer/src/proxy/proxy.js#L106 should no longer be hardcoded but usse a configmap to load like above
Given we will have to upgrade the webtop often, we need to be able to easily adjust the requierd proxying in the wrongsecrets-balancer. That is why we need a configmap that contains a mapping for:
so, something like:
incomingurl1
incomingurl2
incomingurl3
incomingurl4
incomingurl5
incomingurl6
incomingurl7
incomingurl8withwildcard
incomingurl9
incomingurl10
incomingurl10
the deployment should mount the configmap in so that the balancer its code should be able to read it. both the deployment and balancer code need to be adjusted.
https://github.com/OWASP/wrongsecrets-ctf-party/blob/main/wrongsecrets-balancer/src/proxy/proxy.js#L106 should no longer be hardcoded but usse a configmap to load like above