Rethink how we're storing the routing configuration

[whitlockjc]

Right now, we're using a mix annotations to perform the wiring of the router. This is working fine but with #18 and #29, we're quickly getting to the point where we're adding more and more things. Maybe it's time we look into storing JSON in a single annotation?

[mpnally]

What would be the advantage?

[whitlockjc]

I created this when I thought we were going to add yet another configuration annotation for #29. We ended up not doing that so we can keep this in the backlog for now. But to answer your question, Kubernetes stuff structured data (JSON) into annotations when it makes sense and I think when our routing rules become more complex and/or repetitive, we might want to at least revisit this. But nothing is changing right now because it's not necessary now that #29 is done without a new annotation.

[whitlockjc]

This is not important right now and can be re-opened if/when it ever is.