Mixing
GCP, Autoscaling on internal load balancer
I managed to set up autoscaling based on an external load balancer, but I didn't find a way to do the same for an internal load balancer.
Is this feature supported, how to go about auto-scaling my instance group based on the internal load balancer?
The issue is, when you configure an instance group to scale by HTTP requests, you need an HTTP load balancer, which is internet facing, So, the UDP load balancer, which can be internal doesn't work for that.
google-cloud-platform
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
add a comment |
I managed to set up autoscaling based on an external load balancer, but I didn't find a way to do the same for an internal load balancer.
Is this feature supported, how to go about auto-scaling my instance group based on the internal load balancer?
The issue is, when you configure an instance group to scale by HTTP requests, you need an HTTP load balancer, which is internet facing, So, the UDP load balancer, which can be internal doesn't work for that.
google-cloud-platform
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
Yes, this is supported. What have you tried and what problems are you seeing (provide details)?
– John Hanley
Dec 19 '18 at 20:31
add a comment |
I managed to set up autoscaling based on an external load balancer, but I didn't find a way to do the same for an internal load balancer.
Is this feature supported, how to go about auto-scaling my instance group based on the internal load balancer?
The issue is, when you configure an instance group to scale by HTTP requests, you need an HTTP load balancer, which is internet facing, So, the UDP load balancer, which can be internal doesn't work for that.
google-cloud-platform
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
I managed to set up autoscaling based on an external load balancer, but I didn't find a way to do the same for an internal load balancer.
Is this feature supported, how to go about auto-scaling my instance group based on the internal load balancer?
The issue is, when you configure an instance group to scale by HTTP requests, you need an HTTP load balancer, which is internet facing, So, the UDP load balancer, which can be internal doesn't work for that.
google-cloud-platform
google-cloud-platform
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
edited Dec 20 '18 at 9:11
aclokay
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
asked Dec 19 '18 at 15:56
aclokayaclokay
1,1351131
1,1351131
Yes, this is supported. What have you tried and what problems are you seeing (provide details)?
– John Hanley
Dec 19 '18 at 20:31
add a comment |
Yes, this is supported. What have you tried and what problems are you seeing (provide details)?
– John Hanley
Dec 19 '18 at 20:31
Yes, this is supported. What have you tried and what problems are you seeing (provide details)?
– John Hanley
Dec 19 '18 at 20:31
Yes, this is supported. What have you tried and what problems are you seeing (provide details)?
– John Hanley
Dec 19 '18 at 20:31
add a comment |
2 Answers
2
active
oldest
votes
The Internal Load Balancer uses a backend service which can use a managed instance group. You can assign a managed instance group to the backend or target pools of both internal and network load balancers.
Keep in mind that the Network Load Balancer uses target pools instead of backend services, but target pools can use managed instance groups as well.
Take a look at the documentation for more details. Alternatively I found this and this posts that I believe can be useful to you.
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
add a comment |
From your last comment:
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doesn't support http load balancing..
As stated in the Internal Load Balancing Concepts, "internal client requests stay internal to your VPC network and region", so there is neither need of HTTP here, nor a multi-regional setup.
On the same page, under section "About Internal Load Balancing", the schema shows a classic load balancing architecture, featuring one global (http) and multiple internal (tcp/udp) load balancers for each region.
Further on, under "Deploying Internal Load Balancing with clients across VPN or Interconnect", the following is stated in an "Important" note:
Internal Load Balancing is a regional product. [...] An internal load balancer cannot forward or receive traffic to and from VM instances in other regions.
Basically, if your managed instance group has instances across multiple regions, then you need an external load balancer, but if all your instances are within the same region (instances can be split across zones within this same region, e.g. us-west1-a/b/c), then you can rely on an internal load balancer.
answered Jan 2 at 13:01
alpalp
3036
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53854891%2fgcp-autoscaling-on-internal-load-balancer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Internal Load Balancer uses a backend service which can use a managed instance group. You can assign a managed instance group to the backend or target pools of both internal and network load balancers.
Keep in mind that the Network Load Balancer uses target pools instead of backend services, but target pools can use managed instance groups as well.
Take a look at the documentation for more details. Alternatively I found this and this posts that I believe can be useful to you.
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
add a comment |
The Internal Load Balancer uses a backend service which can use a managed instance group. You can assign a managed instance group to the backend or target pools of both internal and network load balancers.
Keep in mind that the Network Load Balancer uses target pools instead of backend services, but target pools can use managed instance groups as well.
Take a look at the documentation for more details. Alternatively I found this and this posts that I believe can be useful to you.
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
add a comment |
The Internal Load Balancer uses a backend service which can use a managed instance group. You can assign a managed instance group to the backend or target pools of both internal and network load balancers.
Keep in mind that the Network Load Balancer uses target pools instead of backend services, but target pools can use managed instance groups as well.
Take a look at the documentation for more details. Alternatively I found this and this posts that I believe can be useful to you.
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
The Internal Load Balancer uses a backend service which can use a managed instance group. You can assign a managed instance group to the backend or target pools of both internal and network load balancers.
Keep in mind that the Network Load Balancer uses target pools instead of backend services, but target pools can use managed instance groups as well.
Take a look at the documentation for more details. Alternatively I found this and this posts that I believe can be useful to you.
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
edited Dec 21 '18 at 7:42
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
answered Dec 19 '18 at 16:16
MaximMaxim
1,553211
1,553211
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
add a comment |
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I know it's supported on the external load balancer, but does it on the INTERNAL one..
– aclokay
Dec 20 '18 at 7:55
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
I got the error requiring an HTTP load balaner, which is by definition internet facing. and only the UDP is internal.
– aclokay
Dec 20 '18 at 9:10
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
@aclokay I've updated my answer. I apologize for the misunderstanding.
– Maxim
Dec 21 '18 at 7:44
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doens't support http load balancing..
– aclokay
Dec 25 '18 at 8:24
add a comment |
From your last comment:
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doesn't support http load balancing..
As stated in the Internal Load Balancing Concepts, "internal client requests stay internal to your VPC network and region", so there is neither need of HTTP here, nor a multi-regional setup.
On the same page, under section "About Internal Load Balancing", the schema shows a classic load balancing architecture, featuring one global (http) and multiple internal (tcp/udp) load balancers for each region.
Further on, under "Deploying Internal Load Balancing with clients across VPN or Interconnect", the following is stated in an "Important" note:
Internal Load Balancing is a regional product. [...] An internal load balancer cannot forward or receive traffic to and from VM instances in other regions.
Basically, if your managed instance group has instances across multiple regions, then you need an external load balancer, but if all your instances are within the same region (instances can be split across zones within this same region, e.g. us-west1-a/b/c), then you can rely on an internal load balancer.
answered Jan 2 at 13:01
alpalp
3036
add a comment |
From your last comment:
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doesn't support http load balancing..
As stated in the Internal Load Balancing Concepts, "internal client requests stay internal to your VPC network and region", so there is neither need of HTTP here, nor a multi-regional setup.
On the same page, under section "About Internal Load Balancing", the schema shows a classic load balancing architecture, featuring one global (http) and multiple internal (tcp/udp) load balancers for each region.
Further on, under "Deploying Internal Load Balancing with clients across VPN or Interconnect", the following is stated in an "Important" note:
Internal Load Balancing is a regional product. [...] An internal load balancer cannot forward or receive traffic to and from VM instances in other regions.
Basically, if your managed instance group has instances across multiple regions, then you need an external load balancer, but if all your instances are within the same region (instances can be split across zones within this same region, e.g. us-west1-a/b/c), then you can rely on an internal load balancer.
answered Jan 2 at 13:01
alpalp
3036
add a comment |
From your last comment:
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doesn't support http load balancing..
As stated in the Internal Load Balancing Concepts, "internal client requests stay internal to your VPC network and region", so there is neither need of HTTP here, nor a multi-regional setup.
On the same page, under section "About Internal Load Balancing", the schema shows a classic load balancing architecture, featuring one global (http) and multiple internal (tcp/udp) load balancers for each region.
Further on, under "Deploying Internal Load Balancing with clients across VPN or Interconnect", the following is stated in an "Important" note:
Internal Load Balancing is a regional product. [...] An internal load balancer cannot forward or receive traffic to and from VM instances in other regions.
Basically, if your managed instance group has instances across multiple regions, then you need an external load balancer, but if all your instances are within the same region (instances can be split across zones within this same region, e.g. us-west1-a/b/c), then you can rely on an internal load balancer.
answered Jan 2 at 13:01
alpalp
3036
From your last comment:
I'm not able to setup a TCP load balancer which has a backend service, I only get a REGIONAL backend service, which doesn't support http load balancing..
As stated in the Internal Load Balancing Concepts, "internal client requests stay internal to your VPC network and region", so there is neither need of HTTP here, nor a multi-regional setup.
On the same page, under section "About Internal Load Balancing", the schema shows a classic load balancing architecture, featuring one global (http) and multiple internal (tcp/udp) load balancers for each region.
Further on, under "Deploying Internal Load Balancing with clients across VPN or Interconnect", the following is stated in an "Important" note:
Internal Load Balancing is a regional product. [...] An internal load balancer cannot forward or receive traffic to and from VM instances in other regions.
Basically, if your managed instance group has instances across multiple regions, then you need an external load balancer, but if all your instances are within the same region (instances can be split across zones within this same region, e.g. us-west1-a/b/c), then you can rely on an internal load balancer.
answered Jan 2 at 13:01
alpalp
3036
answered Jan 2 at 13:01
alpalp
3036
answered Jan 2 at 13:01
alpalp
3036
answered Jan 2 at 13:01
alpalp
3036
3036
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53854891%2fgcp-autoscaling-on-internal-load-balancer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Yes, this is supported. What have you tried and what problems are you seeing (provide details)?
– John Hanley
Dec 19 '18 at 20:31