Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for backend type and instance group backend #34

Open
riupie opened this issue Apr 28, 2021 · 2 comments
Open

Add support for backend type and instance group backend #34

riupie opened this issue Apr 28, 2021 · 2 comments
Labels
enhancement New feature or request P2 high priority issues triaged Scoped and ready for work

Comments

@riupie
Copy link

riupie commented Apr 28, 2021

When we create network load balancer in GCP, we can choose:

  • Single region or Multi region
  • Backend type between target pool/instance and backend service (for now it only support target)

But it seems this module doesn't yet has support for this feature. It would be good if you guys can add this feature in future release.

Thanks.

@betsy-lichtenberg
Copy link

betsy-lichtenberg commented Jul 13, 2021

Adding some more info to this issue.

The classic "Network Load Balancer" (aka external TCP/UDP) has target pool backends.

The new external TCP/UDP load balancer has backends that use backend services instead of target pools.
Here's a document that discusses the two architectures (target pool vs backend service):
https://cloud.google.com/load-balancing/docs/network#architecture

Here's more conceptual info about the backend service-based architecture:
https://cloud.google.com/load-balancing/docs/network/networklb-backend-service

Here's an example that uses a backend service:
https://cloud.google.com/load-balancing/docs/network/setting-up-network-backend-service

Here's a document that shows how to migrate a target pool-based LB to a backend service-based LB:
https://cloud.google.com/load-balancing/docs/network/transition-to-backend-services

@github-actions
Copy link

github-actions bot commented Dec 8, 2021

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Dec 8, 2021
@morgante morgante added enhancement New feature or request P2 high priority issues triaged Scoped and ready for work and removed Stale labels Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P2 high priority issues triaged Scoped and ready for work
Projects
None yet
Development

No branches or pull requests

3 participants