We may not actually need this anymore because of the wildcard routing, which would reduce complexity.
I don't think it's a sustainable pattern to model the env values explicity. Otherwise we'll have to update them whenever a chart changes its values. Instead, we should probably either just store them as a json blob or as a one-to-many relation of (env values)n->1(environments) with env vales having a key and value.
Stef Dunlap (1048bd53) at 18 Mar 18:38
Fixup inconsisten API resource endpoints
Stef Dunlap (43a1a6af) at 12 Mar 20:06
Add log and event resources
Stef Dunlap (1b324b06) at 11 Mar 20:48
Update spec
Stef Dunlap (dd66acc4) at 11 Mar 20:02
Update README add documentation
Stef Dunlap (b90d0925) at 11 Mar 19:55
Initial commit!
Stef Dunlap (5e764b14) at 11 Mar 19:51
Initial commit
Stef Dunlap (579a45c3) at 05 Mar 21:50
README: add apparmor instructioins
@jforrester it looks like this is a real failure
My understanding was @vwalters was going to add these back as he fixed them.
Bug: T359179
Stef Dunlap (3dc56797) at 29 Feb 22:31
Update aw-ci-chart
Stef Dunlap (8045039b) at 29 Feb 22:11
Use explicit loopback IP for evaluators instead of localhost
Stef Dunlap (72ab8151) at 29 Feb 21:58
Add ipv6 hostAlias
Stef Dunlap (ed541616) at 27 Feb 21:20
Fixup new HTTPScaledObject spec
Bug: T352062