What does Ingress have to do with Kubernetes service loadbalancer?
This is what I define in k8s.yml file:
apiVersion: v1
kind: Service
metadata:
name: myservice
namespace: mynamespace
labels:
app: myservice
annotations:
service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
external-dns.alpha.kubernetes.io/hostname: "myservice."
spec:
selector:
app: myservice
type: LoadBalancer
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
Running this command:
kubectl describe service myservice
gives me the "LoadBalancer Ingress" like this:
Type: LoadBalancer IP:
25.0.162.225 LoadBalancer Ingress: internal-a9716e......us-west-2.elb.amazonaws.com
As I understand, the publishing type I'm using is "LoadBalancer" which helps me expose my Service to external IP address (refer https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/).
And the Ingress is a different thing which sits in front of the Services and I didn't define it in my yml file. (refer: https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0)
With the "LoadBalancer Ingress" I'm able to access my Service from outside the cluster, but I don't understand why it's called "LoadBalancer Ingress"? What does it have to do with Ingress? Or is it true that every load balancer is equipped with an Ingress for the Service exposing purpose?
kubernetes kubernetes-ingress internal-load-balancer asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
add a comment |
This is what I define in k8s.yml file:
apiVersion: v1
kind: Service
metadata:
name: myservice
namespace: mynamespace
labels:
app: myservice
annotations:
service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
external-dns.alpha.kubernetes.io/hostname: "myservice."
spec:
selector:
app: myservice
type: LoadBalancer
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
Running this command:
kubectl describe service myservice
gives me the "LoadBalancer Ingress" like this:
Type: LoadBalancer IP:
25.0.162.225 LoadBalancer Ingress: internal-a9716e......us-west-2.elb.amazonaws.com
As I understand, the publishing type I'm using is "LoadBalancer" which helps me expose my Service to external IP address (refer https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/).
And the Ingress is a different thing which sits in front of the Services and I didn't define it in my yml file. (refer: https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0)
With the "LoadBalancer Ingress" I'm able to access my Service from outside the cluster, but I don't understand why it's called "LoadBalancer Ingress"? What does it have to do with Ingress? Or is it true that every load balancer is equipped with an Ingress for the Service exposing purpose?
kubernetes kubernetes-ingress internal-load-balancer asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
The ingress you seeing there is not the kubernetes ingress thing , its just the amazon naming convention that they use this word in thier implemnetation of exposing a service over external load balancer
– Ijaz Ahmad Khan
Nov 20 '18 at 21:32
Yes, I found it also a bit confusing.
– Nepomucen
Nov 29 '18 at 11:25
add a comment |
This is what I define in k8s.yml file:
apiVersion: v1
kind: Service
metadata:
name: myservice
namespace: mynamespace
labels:
app: myservice
annotations:
service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
external-dns.alpha.kubernetes.io/hostname: "myservice."
spec:
selector:
app: myservice
type: LoadBalancer
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
Running this command:
kubectl describe service myservice
gives me the "LoadBalancer Ingress" like this:
Type: LoadBalancer IP:
25.0.162.225 LoadBalancer Ingress: internal-a9716e......us-west-2.elb.amazonaws.com
As I understand, the publishing type I'm using is "LoadBalancer" which helps me expose my Service to external IP address (refer https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/).
And the Ingress is a different thing which sits in front of the Services and I didn't define it in my yml file. (refer: https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0)
With the "LoadBalancer Ingress" I'm able to access my Service from outside the cluster, but I don't understand why it's called "LoadBalancer Ingress"? What does it have to do with Ingress? Or is it true that every load balancer is equipped with an Ingress for the Service exposing purpose?
kubernetes kubernetes-ingress internal-load-balancer asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
This is what I define in k8s.yml file:
apiVersion: v1
kind: Service
metadata:
name: myservice
namespace: mynamespace
labels:
app: myservice
annotations:
service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
external-dns.alpha.kubernetes.io/hostname: "myservice."
spec:
selector:
app: myservice
type: LoadBalancer
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
Running this command:
kubectl describe service myservice
gives me the "LoadBalancer Ingress" like this:
Type: LoadBalancer IP:
25.0.162.225 LoadBalancer Ingress: internal-a9716e......us-west-2.elb.amazonaws.com
As I understand, the publishing type I'm using is "LoadBalancer" which helps me expose my Service to external IP address (refer https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/).
And the Ingress is a different thing which sits in front of the Services and I didn't define it in my yml file. (refer: https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0)
With the "LoadBalancer Ingress" I'm able to access my Service from outside the cluster, but I don't understand why it's called "LoadBalancer Ingress"? What does it have to do with Ingress? Or is it true that every load balancer is equipped with an Ingress for the Service exposing purpose?
kubernetes kubernetes-ingress internal-load-balancer kubernetes kubernetes-ingress internal-load-balancer asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
asked Nov 20 '18 at 19:07
Duc TranDuc Tran
3,41332436
3,41332436
The ingress you seeing there is not the kubernetes ingress thing , its just the amazon naming convention that they use this word in thier implemnetation of exposing a service over external load balancer
– Ijaz Ahmad Khan
Nov 20 '18 at 21:32
Yes, I found it also a bit confusing.
– Nepomucen
Nov 29 '18 at 11:25
add a comment |
The ingress you seeing there is not the kubernetes ingress thing , its just the amazon naming convention that they use this word in thier implemnetation of exposing a service over external load balancer
– Ijaz Ahmad Khan
Nov 20 '18 at 21:32
Yes, I found it also a bit confusing.
– Nepomucen
Nov 29 '18 at 11:25
The ingress you seeing there is not the kubernetes ingress thing , its just the amazon naming convention that they use this word in thier implemnetation of exposing a service over external load balancer
– Ijaz Ahmad Khan
Nov 20 '18 at 21:32
The ingress you seeing there is not the kubernetes ingress thing , its just the amazon naming convention that they use this word in thier implemnetation of exposing a service over external load balancer
– Ijaz Ahmad Khan
Nov 20 '18 at 21:32
Yes, I found it also a bit confusing.
– Nepomucen
Nov 29 '18 at 11:25
Yes, I found it also a bit confusing.
– Nepomucen
Nov 29 '18 at 11:25
add a comment |
1 Answer
1
active
oldest
votes
Ingress is an abstract definition of what to expose and how. Usually refers to HTTP(S) traffic, but with some fiddling can also other modes/protocols..
Ingress Controller is a particular implementation that will realize your Ingress defined expectations using a specific piece of software. Be it Nginx, Traefik or some other solution, potentially dedicated to particular cloud provider.
They will use Service objects as means of finding what are the endpoints to use for specific traffing that reached them. It's of no consequence if this is headless, ClusterIP, NodePort or LoadBalancer type of service.
That said, LoadBalancer type service exposes your service on a, surprise, loadbalancer. Again, usually related to your cloud provider. It's a completely different way of exposing your service, as is NodePort type.
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
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%2f53399894%2fwhat-does-ingress-have-to-do-with-kubernetes-service-loadbalancer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ingress is an abstract definition of what to expose and how. Usually refers to HTTP(S) traffic, but with some fiddling can also other modes/protocols..
Ingress Controller is a particular implementation that will realize your Ingress defined expectations using a specific piece of software. Be it Nginx, Traefik or some other solution, potentially dedicated to particular cloud provider.
They will use Service objects as means of finding what are the endpoints to use for specific traffing that reached them. It's of no consequence if this is headless, ClusterIP, NodePort or LoadBalancer type of service.
That said, LoadBalancer type service exposes your service on a, surprise, loadbalancer. Again, usually related to your cloud provider. It's a completely different way of exposing your service, as is NodePort type.
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
add a comment |
Ingress is an abstract definition of what to expose and how. Usually refers to HTTP(S) traffic, but with some fiddling can also other modes/protocols..
Ingress Controller is a particular implementation that will realize your Ingress defined expectations using a specific piece of software. Be it Nginx, Traefik or some other solution, potentially dedicated to particular cloud provider.
They will use Service objects as means of finding what are the endpoints to use for specific traffing that reached them. It's of no consequence if this is headless, ClusterIP, NodePort or LoadBalancer type of service.
That said, LoadBalancer type service exposes your service on a, surprise, loadbalancer. Again, usually related to your cloud provider. It's a completely different way of exposing your service, as is NodePort type.
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
add a comment |
Ingress is an abstract definition of what to expose and how. Usually refers to HTTP(S) traffic, but with some fiddling can also other modes/protocols..
Ingress Controller is a particular implementation that will realize your Ingress defined expectations using a specific piece of software. Be it Nginx, Traefik or some other solution, potentially dedicated to particular cloud provider.
They will use Service objects as means of finding what are the endpoints to use for specific traffing that reached them. It's of no consequence if this is headless, ClusterIP, NodePort or LoadBalancer type of service.
That said, LoadBalancer type service exposes your service on a, surprise, loadbalancer. Again, usually related to your cloud provider. It's a completely different way of exposing your service, as is NodePort type.
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
Ingress is an abstract definition of what to expose and how. Usually refers to HTTP(S) traffic, but with some fiddling can also other modes/protocols..
Ingress Controller is a particular implementation that will realize your Ingress defined expectations using a specific piece of software. Be it Nginx, Traefik or some other solution, potentially dedicated to particular cloud provider.
They will use Service objects as means of finding what are the endpoints to use for specific traffing that reached them. It's of no consequence if this is headless, ClusterIP, NodePort or LoadBalancer type of service.
That said, LoadBalancer type service exposes your service on a, surprise, loadbalancer. Again, usually related to your cloud provider. It's a completely different way of exposing your service, as is NodePort type.
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
answered Nov 20 '18 at 19:20
Radek 'Goblin' PieczonkaRadek 'Goblin' Pieczonka
8,2941424
8,2941424
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%2f53399894%2fwhat-does-ingress-have-to-do-with-kubernetes-service-loadbalancer%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
The ingress you seeing there is not the kubernetes ingress thing , its just the amazon naming convention that they use this word in thier implemnetation of exposing a service over external load balancer
– Ijaz Ahmad Khan
Nov 20 '18 at 21:32
Yes, I found it also a bit confusing.
– Nepomucen
Nov 29 '18 at 11:25