Is it possible to create an GKE ingress controller with internal IP?
up vote
0
down vote
favorite
When I create a GKE ingress controller, by default it created a public ip.
Is it possible to create an GKE ingress controller with internal IP?
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external.
However, if I expose my service as LoadBalancer,
I can specify the type of IP.
annotations: cloud.google.com/load-balancer
-type: "Internal"
google-cloud-platform kubernetes-ingress gke nginx-ingress asked Nov 21 at 16:37
Sunil Gajula
74
add a comment |
up vote
0
down vote
favorite
When I create a GKE ingress controller, by default it created a public ip.
Is it possible to create an GKE ingress controller with internal IP?
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external.
However, if I expose my service as LoadBalancer,
I can specify the type of IP.
annotations: cloud.google.com/load-balancer
-type: "Internal"
google-cloud-platform kubernetes-ingress gke nginx-ingress asked Nov 21 at 16:37
Sunil Gajula
74
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I create a GKE ingress controller, by default it created a public ip.
Is it possible to create an GKE ingress controller with internal IP?
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external.
However, if I expose my service as LoadBalancer,
I can specify the type of IP.
annotations: cloud.google.com/load-balancer
-type: "Internal"
google-cloud-platform kubernetes-ingress gke nginx-ingress asked Nov 21 at 16:37
Sunil Gajula
74
When I create a GKE ingress controller, by default it created a public ip.
Is it possible to create an GKE ingress controller with internal IP?
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external.
However, if I expose my service as LoadBalancer,
I can specify the type of IP.
annotations: cloud.google.com/load-balancer
-type: "Internal"
google-cloud-platform kubernetes-ingress gke nginx-ingress google-cloud-platform kubernetes-ingress gke nginx-ingress asked Nov 21 at 16:37
Sunil Gajula
74
asked Nov 21 at 16:37
Sunil Gajula
74
edited Nov 22 at 10:54
asked Nov 21 at 16:37
Sunil Gajula
74
asked Nov 21 at 16:37
Sunil Gajula
74
asked Nov 21 at 16:37
Sunil Gajula
74
74
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
It sounds like an internal loadbalancer is what you are looking for. An internal load balancer will create a private load balancer ingress IP. This will make your services accessible to the network outside of the cluster, more specifically, "on the network within the same compute region from an IP range in the user’s subnet.", not exposed to the public internet.
Pricing information as well as examples YAML & kubectl commands are within the document.
answered Nov 21 at 20:05
xavierc
415
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It sounds like an internal loadbalancer is what you are looking for. An internal load balancer will create a private load balancer ingress IP. This will make your services accessible to the network outside of the cluster, more specifically, "on the network within the same compute region from an IP range in the user’s subnet.", not exposed to the public internet.
Pricing information as well as examples YAML & kubectl commands are within the document.
answered Nov 21 at 20:05
xavierc
415
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
add a comment |
up vote
0
down vote
It sounds like an internal loadbalancer is what you are looking for. An internal load balancer will create a private load balancer ingress IP. This will make your services accessible to the network outside of the cluster, more specifically, "on the network within the same compute region from an IP range in the user’s subnet.", not exposed to the public internet.
Pricing information as well as examples YAML & kubectl commands are within the document.
answered Nov 21 at 20:05
xavierc
415
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
add a comment |
up vote
0
down vote
up vote
0
down vote
It sounds like an internal loadbalancer is what you are looking for. An internal load balancer will create a private load balancer ingress IP. This will make your services accessible to the network outside of the cluster, more specifically, "on the network within the same compute region from an IP range in the user’s subnet.", not exposed to the public internet.
Pricing information as well as examples YAML & kubectl commands are within the document.
answered Nov 21 at 20:05
xavierc
415
It sounds like an internal loadbalancer is what you are looking for. An internal load balancer will create a private load balancer ingress IP. This will make your services accessible to the network outside of the cluster, more specifically, "on the network within the same compute region from an IP range in the user’s subnet.", not exposed to the public internet.
Pricing information as well as examples YAML & kubectl commands are within the document.
answered Nov 21 at 20:05
xavierc
415
answered Nov 21 at 20:05
xavierc
415
answered Nov 21 at 20:05
xavierc
415
answered Nov 21 at 20:05
xavierc
415
415
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
add a comment |
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
I have exposed my service as type Ingress, I do not have an option to specify if my ip has to be internal or external. However, if I expose my service as LoadBalancer, I can specify the type of IP. annotations: cloud.google.com/load-balancer-type: "Internal"
– Sunil Gajula
Nov 22 at 4:01
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
Ingress' are used for exposing internal services externally via HTTP &/or HTTPS. You will not be able to create an internal ingress. Best to explore the option of internal load balancers mentioned previously.
– xavierc
Nov 22 at 20:48
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%2f53416699%2fis-it-possible-to-create-an-gke-ingress-controller-with-internal-ip%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
