Create Traefik ingressroutes for `docker{1-3}` traffic

[clee231]

Currently, some webapps are being hosted on docker{1-3}.

Traffic to/from these webapps must be maintained before the Kubernetes cluster can be switched to accept traffic for app.acm.cs.uic.edu.

Acceptance Criteria

• Gather a list of webapps accepting traffic on docker{1-3}. Be sure to note the instance and external hostname being used.
• Create IngressRoute resources within Kubernetes to handle the proxying of this traffic.

[clee231]

The following are all the Traefik route definitions within the manage repo for docker{1-3} nodes.

Docker 1 (Supporting ACME)

• flourish-2023
  • Hosts: sparkhacksatuic.com,www.sparkhacksatuic.com

Docker 2

• flourish-2023
  • Hosts: flourishconf.com

Docker 3

• registration-bot
  • Hosts: registration-bot.acmuic.org (This is only available on internal DNS.)

It seems that all nodes are running traefik on ports 80 & 443, however only docker1 has ACME configured. It is not a mistake that both Docker1-2 have apps named flourish-2023. That's is what they are named... 🤔

[clee231]

#59 was merged to address this.
TLS certificates still need to be added for Traefik to correctly secure traffic.