feat(router): static routes support #404
Conversation
villevsv-upcloud
force-pushed
the
feat/static-routes
branch
from
3b11754 to
5d49788
Compare
| @@ -10,6 +10,10 @@ variable "zone" { | |||
|
|
|||
| resource "upcloud_router" "this" { | |||
| name = "${var.prefix}router" | |||
|
|
|||
| lifecycle { | |||
| ignore_changes = [static_route] | |||
There was a problem hiding this comment.
Does the gateway automatically set static_routes to the router? Could we somehow handle that automatic route so that end-user does not have to use lifecycle.ignore_changes 🤔 Or is it something we could instruct user to do themselves, like the router creation with Kubernetes clusters.
There was a problem hiding this comment.
Added a comment to the documentation for now.
There was a problem hiding this comment.
The static routes automatically set by the gateway seem to be in link-local address space (169.254.0.0/16). Thus, they should not collide with values expected from user. Maybe some sort special value would work here, but that would require more investigating/testing.
There was a problem hiding this comment.
Probably good to merge this like this to unblock the release and then try to add fix or workaround for this later 🤔 I was also trying to think of some nice way of fixing this, but no good ideas this far.
Co-authored-by: villevsv-upcloud <[email protected]>
No description provided.