You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement policy based routing for client projects - where next hop is routed through an internal LB and based on a packets destination address including client to client east-west traffic
#854
Open
fmichaelobrien opened this issue
Feb 23, 2024
· 0 comments
see network architecture that allows for both shared VPC service projects and client specific VPCs.
check 1.6.x for inclusion of GoogleCloudPlatform/magic-modules#9320 late october 2023
https://releases.hashicorp.com/terraform/
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/network_connectivity_policy_based_route
https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest/v1/projects.locations.global.policyBasedRoutes
https://cloud.google.com/vpc/docs/use-policy-based-routes#api
hashicorp/terraform-provider-google#15414
GoogleCloudPlatform/magic-modules#9320
terraform-google-modules/docs-examples#579
https://cloud.google.com/vpc/docs/use-policy-based-routes#create-within-vpc
https://cloud.google.com/vpc/docs/policy-based-routes
https://medium.com/google-cloud/why-policy-based-routing-is-a-game-changer-f4c6a7badccb
https://codelabs.developers.google.com/codelabs/cloudnet-pbr#0
krm for config-controller - there is some discussion on missing krm wrapper around the PBR api - investigate
documentation
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/Architecture
The text was updated successfully, but these errors were encountered: