Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create proxy and websocket configuration configmap for wrongsecrets-balancer #252

Open
commjoen opened this issue May 26, 2023 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@commjoen
Copy link
Collaborator

commjoen commented May 26, 2023

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

@commjoen commjoen added help wanted Extra attention is needed hacktoberfest labels Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant