Ingress service type
I understand the principle of Ingress, how it routes to services by feeding an Ingress resource to the Ingress controller.
I use Docker for mac with the following Ingress controller: https://github.com/kubernetes/ingress-nginx/blob/master/docs/deploy/index.md#docker-for-mac
There is just one thing I don't quite understand, and that is what type of service you are supposed to use.
Is it ok to use replica sets as you would do with regular load balancer services, and should you provide a resource of 'Kind' 'service' while omitting the 'spec/type' attribute in the service resource altogether?
kubernetes
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
add a comment |
I understand the principle of Ingress, how it routes to services by feeding an Ingress resource to the Ingress controller.
I use Docker for mac with the following Ingress controller: https://github.com/kubernetes/ingress-nginx/blob/master/docs/deploy/index.md#docker-for-mac
There is just one thing I don't quite understand, and that is what type of service you are supposed to use.
Is it ok to use replica sets as you would do with regular load balancer services, and should you provide a resource of 'Kind' 'service' while omitting the 'spec/type' attribute in the service resource altogether?
kubernetes
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
add a comment |
I understand the principle of Ingress, how it routes to services by feeding an Ingress resource to the Ingress controller.
I use Docker for mac with the following Ingress controller: https://github.com/kubernetes/ingress-nginx/blob/master/docs/deploy/index.md#docker-for-mac
There is just one thing I don't quite understand, and that is what type of service you are supposed to use.
Is it ok to use replica sets as you would do with regular load balancer services, and should you provide a resource of 'Kind' 'service' while omitting the 'spec/type' attribute in the service resource altogether?
kubernetes
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
I understand the principle of Ingress, how it routes to services by feeding an Ingress resource to the Ingress controller.
I use Docker for mac with the following Ingress controller: https://github.com/kubernetes/ingress-nginx/blob/master/docs/deploy/index.md#docker-for-mac
There is just one thing I don't quite understand, and that is what type of service you are supposed to use.
Is it ok to use replica sets as you would do with regular load balancer services, and should you provide a resource of 'Kind' 'service' while omitting the 'spec/type' attribute in the service resource altogether?
kubernetes
kubernetes
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
asked Dec 28 '18 at 14:21
TraceTrace
8,10853686
8,10853686
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
For your apps use a Service of type ClusterIP as you would for a cluster-internal Service. This is because they are now internal and it is only the ingress controller which is external. See examples in https://kubernetes.io/docs/concepts/services-networking/ingress/
For the Ingress controller itself you typically use LoadBalancer but it is your choice how you expose themselves ingress controller externally. You can use NodePort if that suits your cluster (e.g. it is on-prem). In that docker for Mac example the ingress controller is LoadBalancer type - https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml This is typically used for cloud providers but docker for Mac supports it - Docker for Mac(Edge) - Kubernetes - LoadBalancer
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
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%2f53959974%2fingress-service-type%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
For your apps use a Service of type ClusterIP as you would for a cluster-internal Service. This is because they are now internal and it is only the ingress controller which is external. See examples in https://kubernetes.io/docs/concepts/services-networking/ingress/
For the Ingress controller itself you typically use LoadBalancer but it is your choice how you expose themselves ingress controller externally. You can use NodePort if that suits your cluster (e.g. it is on-prem). In that docker for Mac example the ingress controller is LoadBalancer type - https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml This is typically used for cloud providers but docker for Mac supports it - Docker for Mac(Edge) - Kubernetes - LoadBalancer
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
add a comment |
For your apps use a Service of type ClusterIP as you would for a cluster-internal Service. This is because they are now internal and it is only the ingress controller which is external. See examples in https://kubernetes.io/docs/concepts/services-networking/ingress/
For the Ingress controller itself you typically use LoadBalancer but it is your choice how you expose themselves ingress controller externally. You can use NodePort if that suits your cluster (e.g. it is on-prem). In that docker for Mac example the ingress controller is LoadBalancer type - https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml This is typically used for cloud providers but docker for Mac supports it - Docker for Mac(Edge) - Kubernetes - LoadBalancer
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
add a comment |
For your apps use a Service of type ClusterIP as you would for a cluster-internal Service. This is because they are now internal and it is only the ingress controller which is external. See examples in https://kubernetes.io/docs/concepts/services-networking/ingress/
For the Ingress controller itself you typically use LoadBalancer but it is your choice how you expose themselves ingress controller externally. You can use NodePort if that suits your cluster (e.g. it is on-prem). In that docker for Mac example the ingress controller is LoadBalancer type - https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml This is typically used for cloud providers but docker for Mac supports it - Docker for Mac(Edge) - Kubernetes - LoadBalancer
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
For your apps use a Service of type ClusterIP as you would for a cluster-internal Service. This is because they are now internal and it is only the ingress controller which is external. See examples in https://kubernetes.io/docs/concepts/services-networking/ingress/
For the Ingress controller itself you typically use LoadBalancer but it is your choice how you expose themselves ingress controller externally. You can use NodePort if that suits your cluster (e.g. it is on-prem). In that docker for Mac example the ingress controller is LoadBalancer type - https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml This is typically used for cloud providers but docker for Mac supports it - Docker for Mac(Edge) - Kubernetes - LoadBalancer
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
answered Dec 28 '18 at 14:53
Ryan DawsonRyan Dawson
3,8723325
3,8723325
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
add a comment |
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
For more on the flow of traffic see stackoverflow.com/questions/53865013/…
– Ryan Dawson
Dec 28 '18 at 14:54
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
Thanks for swift reply!
– Trace
Dec 28 '18 at 14:55
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%2f53959974%2fingress-service-type%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
