How can I create Kubernetes load balancer with an ephemeral IP in GKE?
up vote
0
down vote
favorite
How can I configure a LoadBalancer to retrieve a ephemeral rather than static IP?
I need this so I don't have to WAIT FOR GOOGLE TO INCREASE THE QUOTA FROM 1 IP ADDRRESS... (It's been a long day...)
Normal EnsuringLoadBalancer 3m (x7 over 8m) service-controller Ensuring load balancer
Warning CreatingLoadBalancerFailed 3m (x7 over 8m) service-controller Error creating load balancer (will retry): failed to ensure load balancer for service default/subzero-react: failed to ensure a static IP for load balancer (*****************(default/subzero-react)): error creating gce static IP address: googleapi: Error 403: Quota 'STATIC_ADDRESSES' exceeded. Limit: 1.0 in region us-central1., quotaExceeded
Upon removing the loadBalancerIp
field and recreating the service, it still remains in pending.
This is the output of kubectl get service ****** -o yaml
:
kubectl get service **** -o yaml
apiVersion: v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"api"},"name":"subzero-react","namespace":"default"},"spec":{"ports":[{"name":"http","port":80}],"selector":{"app":"initial-pp3subzero"},"type":"LoadBalancer"}}
creationTimestamp: 2018-11-19T18:04:24Z
labels:
app: api
name: *****************
namespace: default
resourceVersion: "584211"
selfLink: /api/v1/namespaces/default/services/**********
uid: 8c140d40-ec25-11e8-b7b3-42010a8000c2
spec:
clusterIP: 10.7.242.176
externalTrafficPolicy: Cluster
ports:
- name: http
nodePort: 31853
port: 80
protocol: TCP
targetPort: 80
selector:
app: ******************
sessionAffinity: None
type: LoadBalancer
status:
loadBalancer: {}
kubernetes google-cloud-platform google-kubernetes-engine kubernetes-service
add a comment |
up vote
0
down vote
favorite
How can I configure a LoadBalancer to retrieve a ephemeral rather than static IP?
I need this so I don't have to WAIT FOR GOOGLE TO INCREASE THE QUOTA FROM 1 IP ADDRRESS... (It's been a long day...)
Normal EnsuringLoadBalancer 3m (x7 over 8m) service-controller Ensuring load balancer
Warning CreatingLoadBalancerFailed 3m (x7 over 8m) service-controller Error creating load balancer (will retry): failed to ensure load balancer for service default/subzero-react: failed to ensure a static IP for load balancer (*****************(default/subzero-react)): error creating gce static IP address: googleapi: Error 403: Quota 'STATIC_ADDRESSES' exceeded. Limit: 1.0 in region us-central1., quotaExceeded
Upon removing the loadBalancerIp
field and recreating the service, it still remains in pending.
This is the output of kubectl get service ****** -o yaml
:
kubectl get service **** -o yaml
apiVersion: v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"api"},"name":"subzero-react","namespace":"default"},"spec":{"ports":[{"name":"http","port":80}],"selector":{"app":"initial-pp3subzero"},"type":"LoadBalancer"}}
creationTimestamp: 2018-11-19T18:04:24Z
labels:
app: api
name: *****************
namespace: default
resourceVersion: "584211"
selfLink: /api/v1/namespaces/default/services/**********
uid: 8c140d40-ec25-11e8-b7b3-42010a8000c2
spec:
clusterIP: 10.7.242.176
externalTrafficPolicy: Cluster
ports:
- name: http
nodePort: 31853
port: 80
protocol: TCP
targetPort: 80
selector:
app: ******************
sessionAffinity: None
type: LoadBalancer
status:
loadBalancer: {}
kubernetes google-cloud-platform google-kubernetes-engine kubernetes-service
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How can I configure a LoadBalancer to retrieve a ephemeral rather than static IP?
I need this so I don't have to WAIT FOR GOOGLE TO INCREASE THE QUOTA FROM 1 IP ADDRRESS... (It's been a long day...)
Normal EnsuringLoadBalancer 3m (x7 over 8m) service-controller Ensuring load balancer
Warning CreatingLoadBalancerFailed 3m (x7 over 8m) service-controller Error creating load balancer (will retry): failed to ensure load balancer for service default/subzero-react: failed to ensure a static IP for load balancer (*****************(default/subzero-react)): error creating gce static IP address: googleapi: Error 403: Quota 'STATIC_ADDRESSES' exceeded. Limit: 1.0 in region us-central1., quotaExceeded
Upon removing the loadBalancerIp
field and recreating the service, it still remains in pending.
This is the output of kubectl get service ****** -o yaml
:
kubectl get service **** -o yaml
apiVersion: v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"api"},"name":"subzero-react","namespace":"default"},"spec":{"ports":[{"name":"http","port":80}],"selector":{"app":"initial-pp3subzero"},"type":"LoadBalancer"}}
creationTimestamp: 2018-11-19T18:04:24Z
labels:
app: api
name: *****************
namespace: default
resourceVersion: "584211"
selfLink: /api/v1/namespaces/default/services/**********
uid: 8c140d40-ec25-11e8-b7b3-42010a8000c2
spec:
clusterIP: 10.7.242.176
externalTrafficPolicy: Cluster
ports:
- name: http
nodePort: 31853
port: 80
protocol: TCP
targetPort: 80
selector:
app: ******************
sessionAffinity: None
type: LoadBalancer
status:
loadBalancer: {}
kubernetes google-cloud-platform google-kubernetes-engine kubernetes-service
How can I configure a LoadBalancer to retrieve a ephemeral rather than static IP?
I need this so I don't have to WAIT FOR GOOGLE TO INCREASE THE QUOTA FROM 1 IP ADDRRESS... (It's been a long day...)
Normal EnsuringLoadBalancer 3m (x7 over 8m) service-controller Ensuring load balancer
Warning CreatingLoadBalancerFailed 3m (x7 over 8m) service-controller Error creating load balancer (will retry): failed to ensure load balancer for service default/subzero-react: failed to ensure a static IP for load balancer (*****************(default/subzero-react)): error creating gce static IP address: googleapi: Error 403: Quota 'STATIC_ADDRESSES' exceeded. Limit: 1.0 in region us-central1., quotaExceeded
Upon removing the loadBalancerIp
field and recreating the service, it still remains in pending.
This is the output of kubectl get service ****** -o yaml
:
kubectl get service **** -o yaml
apiVersion: v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"api"},"name":"subzero-react","namespace":"default"},"spec":{"ports":[{"name":"http","port":80}],"selector":{"app":"initial-pp3subzero"},"type":"LoadBalancer"}}
creationTimestamp: 2018-11-19T18:04:24Z
labels:
app: api
name: *****************
namespace: default
resourceVersion: "584211"
selfLink: /api/v1/namespaces/default/services/**********
uid: 8c140d40-ec25-11e8-b7b3-42010a8000c2
spec:
clusterIP: 10.7.242.176
externalTrafficPolicy: Cluster
ports:
- name: http
nodePort: 31853
port: 80
protocol: TCP
targetPort: 80
selector:
app: ******************
sessionAffinity: None
type: LoadBalancer
status:
loadBalancer: {}
kubernetes google-cloud-platform google-kubernetes-engine kubernetes-service
kubernetes google-cloud-platform google-kubernetes-engine kubernetes-service
edited Nov 20 at 8:57
asked Nov 19 at 18:14
Chris Stryczynski
3,51242657
3,51242657
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
To not assign a static IP on a GCP load balancer with Kubernetes (default behavior) you generally don't need to specify anything in the loadBalancerIP
service spec as described here and here.
You can delete your service and re-create it without the loadBalancerIP
or you can patch it:
$ kubectl patch service <service-name> -p '{"spec": { "loadBalancerIP": null }}'
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip withloadBalancerIp
- but this has definitely been removed now.
– Chris Stryczynski
Nov 20 at 8:54
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
To not assign a static IP on a GCP load balancer with Kubernetes (default behavior) you generally don't need to specify anything in the loadBalancerIP
service spec as described here and here.
You can delete your service and re-create it without the loadBalancerIP
or you can patch it:
$ kubectl patch service <service-name> -p '{"spec": { "loadBalancerIP": null }}'
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip withloadBalancerIp
- but this has definitely been removed now.
– Chris Stryczynski
Nov 20 at 8:54
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
add a comment |
up vote
1
down vote
To not assign a static IP on a GCP load balancer with Kubernetes (default behavior) you generally don't need to specify anything in the loadBalancerIP
service spec as described here and here.
You can delete your service and re-create it without the loadBalancerIP
or you can patch it:
$ kubectl patch service <service-name> -p '{"spec": { "loadBalancerIP": null }}'
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip withloadBalancerIp
- but this has definitely been removed now.
– Chris Stryczynski
Nov 20 at 8:54
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
add a comment |
up vote
1
down vote
up vote
1
down vote
To not assign a static IP on a GCP load balancer with Kubernetes (default behavior) you generally don't need to specify anything in the loadBalancerIP
service spec as described here and here.
You can delete your service and re-create it without the loadBalancerIP
or you can patch it:
$ kubectl patch service <service-name> -p '{"spec": { "loadBalancerIP": null }}'
To not assign a static IP on a GCP load balancer with Kubernetes (default behavior) you generally don't need to specify anything in the loadBalancerIP
service spec as described here and here.
You can delete your service and re-create it without the loadBalancerIP
or you can patch it:
$ kubectl patch service <service-name> -p '{"spec": { "loadBalancerIP": null }}'
answered Nov 20 at 1:44
Rico
25.1k94864
25.1k94864
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip withloadBalancerIp
- but this has definitely been removed now.
– Chris Stryczynski
Nov 20 at 8:54
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
add a comment |
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip withloadBalancerIp
- but this has definitely been removed now.
– Chris Stryczynski
Nov 20 at 8:54
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip with
loadBalancerIp
- but this has definitely been removed now.– Chris Stryczynski
Nov 20 at 8:54
I deleted it and recreated it without that field but it's been still 14h and still pending. I did initially try to add a static ip with
loadBalancerIp
- but this has definitely been removed now.– Chris Stryczynski
Nov 20 at 8:54
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
Please check your Quotas page and see if you're hitting any of the "In-use IP addresses" limits.
– Asif Tanwir
Nov 23 at 23:25
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53380452%2fhow-can-i-create-kubernetes-load-balancer-with-an-ephemeral-ip-in-gke%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