Scale Azure nginx ingress controller
We have a K8s cluster on Azure (aks). On this cluster, we added a loadbalancer on the setup which installed an nginx-ingress controller.
Looking at the deployments:
addon-http-application-routing-default-http-backend 1
addon-http-application-routing-external-dns 1
addon-http-application-routing-nginx-ingress-controller 1
I see there is 1 of each running. Now I find very little information if these should be scaled (there is 1 pod each) and if they should, how?
I've tried running
kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
Which temporarily scales it to 3 pods, but after a few moments, it is downscaled again.
So again, are these supposed to be scaled? Why? How?
EDIT
For those that missed it like I did: The AKS addon-http-application is not ready for production, it is there to quickly set you up and start experimenting. Which is why I wasn't able to scale it properly.
Read more
azure kubernetes kubernetes-ingress azure-aks nginx-ingress asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
add a comment |
We have a K8s cluster on Azure (aks). On this cluster, we added a loadbalancer on the setup which installed an nginx-ingress controller.
Looking at the deployments:
addon-http-application-routing-default-http-backend 1
addon-http-application-routing-external-dns 1
addon-http-application-routing-nginx-ingress-controller 1
I see there is 1 of each running. Now I find very little information if these should be scaled (there is 1 pod each) and if they should, how?
I've tried running
kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
Which temporarily scales it to 3 pods, but after a few moments, it is downscaled again.
So again, are these supposed to be scaled? Why? How?
EDIT
For those that missed it like I did: The AKS addon-http-application is not ready for production, it is there to quickly set you up and start experimenting. Which is why I wasn't able to scale it properly.
Read more
azure kubernetes kubernetes-ingress azure-aks nginx-ingress asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
You probably better off installing your own ingress (you can follow this guide) and external-dns.
– alev
Nov 15 '18 at 9:32
add a comment |
We have a K8s cluster on Azure (aks). On this cluster, we added a loadbalancer on the setup which installed an nginx-ingress controller.
Looking at the deployments:
addon-http-application-routing-default-http-backend 1
addon-http-application-routing-external-dns 1
addon-http-application-routing-nginx-ingress-controller 1
I see there is 1 of each running. Now I find very little information if these should be scaled (there is 1 pod each) and if they should, how?
I've tried running
kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
Which temporarily scales it to 3 pods, but after a few moments, it is downscaled again.
So again, are these supposed to be scaled? Why? How?
EDIT
For those that missed it like I did: The AKS addon-http-application is not ready for production, it is there to quickly set you up and start experimenting. Which is why I wasn't able to scale it properly.
Read more
azure kubernetes kubernetes-ingress azure-aks nginx-ingress asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
We have a K8s cluster on Azure (aks). On this cluster, we added a loadbalancer on the setup which installed an nginx-ingress controller.
Looking at the deployments:
addon-http-application-routing-default-http-backend 1
addon-http-application-routing-external-dns 1
addon-http-application-routing-nginx-ingress-controller 1
I see there is 1 of each running. Now I find very little information if these should be scaled (there is 1 pod each) and if they should, how?
I've tried running
kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
Which temporarily scales it to 3 pods, but after a few moments, it is downscaled again.
So again, are these supposed to be scaled? Why? How?
EDIT
For those that missed it like I did: The AKS addon-http-application is not ready for production, it is there to quickly set you up and start experimenting. Which is why I wasn't able to scale it properly.
Read more
azure kubernetes kubernetes-ingress azure-aks nginx-ingress azure kubernetes kubernetes-ingress azure-aks nginx-ingress asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
edited Nov 15 '18 at 9:11
RVandersteen
asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
asked Nov 14 '18 at 15:17
RVandersteenRVandersteen
8951129
8951129
You probably better off installing your own ingress (you can follow this guide) and external-dns.
– alev
Nov 15 '18 at 9:32
add a comment |
You probably better off installing your own ingress (you can follow this guide) and external-dns.
– alev
Nov 15 '18 at 9:32
You probably better off installing your own ingress (you can follow this guide) and external-dns.
– alev
Nov 15 '18 at 9:32
You probably better off installing your own ingress (you can follow this guide) and external-dns.
– alev
Nov 15 '18 at 9:32
add a comment |
2 Answers
2
active
oldest
votes
In AKS, being a managed service, this "system" workloads like kube-dns and the ingress controller, are managed by the service itself and they cannot be modified by the user (because they're labeled with addonmanager.kubernetes.io/mode: Reconcile, which forces the current configuration to reflect what's on disk at /etc/kubernetes/addons on the masters).
answered Nov 14 '18 at 22:59
alevalev
1709
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
That's generally the way how you do it:
$ kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
However, I suspect you have an HPA configured which will scale up/down depending on the load or some metrics and has the minReplicas spec set to 1. You can check with:
$ kubectl get hpa
$ kubectl describe hpa <hpa-name>
If that's the case you can scale up by just patching the HPA:
$ kubectl patch hpa <hpa-name> -p '{"spec": {"minReplicas": 3}}'
or edit it manually:
$ kubectl edit hpa <hpa-name>
More information on HPAs here.
And yes, the ingress controllers are supposed to be scaled up and down depending on the load.
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
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%2f53303411%2fscale-azure-nginx-ingress-controller%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
In AKS, being a managed service, this "system" workloads like kube-dns and the ingress controller, are managed by the service itself and they cannot be modified by the user (because they're labeled with addonmanager.kubernetes.io/mode: Reconcile, which forces the current configuration to reflect what's on disk at /etc/kubernetes/addons on the masters).
answered Nov 14 '18 at 22:59
alevalev
1709
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
In AKS, being a managed service, this "system" workloads like kube-dns and the ingress controller, are managed by the service itself and they cannot be modified by the user (because they're labeled with addonmanager.kubernetes.io/mode: Reconcile, which forces the current configuration to reflect what's on disk at /etc/kubernetes/addons on the masters).
answered Nov 14 '18 at 22:59
alevalev
1709
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
In AKS, being a managed service, this "system" workloads like kube-dns and the ingress controller, are managed by the service itself and they cannot be modified by the user (because they're labeled with addonmanager.kubernetes.io/mode: Reconcile, which forces the current configuration to reflect what's on disk at /etc/kubernetes/addons on the masters).
answered Nov 14 '18 at 22:59
alevalev
1709
In AKS, being a managed service, this "system" workloads like kube-dns and the ingress controller, are managed by the service itself and they cannot be modified by the user (because they're labeled with addonmanager.kubernetes.io/mode: Reconcile, which forces the current configuration to reflect what's on disk at /etc/kubernetes/addons on the masters).
answered Nov 14 '18 at 22:59
alevalev
1709
answered Nov 14 '18 at 22:59
alevalev
1709
answered Nov 14 '18 at 22:59
alevalev
1709
answered Nov 14 '18 at 22:59
alevalev
1709
1709
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
Does this mean that we do not have to 'care' about it and that aks will handle autoscaling / redundancy etc for it ?
– RVandersteen
Nov 15 '18 at 8:39
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
I guess I found the answer - see my edit
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
That's generally the way how you do it:
$ kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
However, I suspect you have an HPA configured which will scale up/down depending on the load or some metrics and has the minReplicas spec set to 1. You can check with:
$ kubectl get hpa
$ kubectl describe hpa <hpa-name>
If that's the case you can scale up by just patching the HPA:
$ kubectl patch hpa <hpa-name> -p '{"spec": {"minReplicas": 3}}'
or edit it manually:
$ kubectl edit hpa <hpa-name>
More information on HPAs here.
And yes, the ingress controllers are supposed to be scaled up and down depending on the load.
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
That's generally the way how you do it:
$ kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
However, I suspect you have an HPA configured which will scale up/down depending on the load or some metrics and has the minReplicas spec set to 1. You can check with:
$ kubectl get hpa
$ kubectl describe hpa <hpa-name>
If that's the case you can scale up by just patching the HPA:
$ kubectl patch hpa <hpa-name> -p '{"spec": {"minReplicas": 3}}'
or edit it manually:
$ kubectl edit hpa <hpa-name>
More information on HPAs here.
And yes, the ingress controllers are supposed to be scaled up and down depending on the load.
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
That's generally the way how you do it:
$ kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
However, I suspect you have an HPA configured which will scale up/down depending on the load or some metrics and has the minReplicas spec set to 1. You can check with:
$ kubectl get hpa
$ kubectl describe hpa <hpa-name>
If that's the case you can scale up by just patching the HPA:
$ kubectl patch hpa <hpa-name> -p '{"spec": {"minReplicas": 3}}'
or edit it manually:
$ kubectl edit hpa <hpa-name>
More information on HPAs here.
And yes, the ingress controllers are supposed to be scaled up and down depending on the load.
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
That's generally the way how you do it:
$ kubectl scale deployment addon-http-application-routing-nginx-ingress-controller --replicas=3
However, I suspect you have an HPA configured which will scale up/down depending on the load or some metrics and has the minReplicas spec set to 1. You can check with:
$ kubectl get hpa
$ kubectl describe hpa <hpa-name>
If that's the case you can scale up by just patching the HPA:
$ kubectl patch hpa <hpa-name> -p '{"spec": {"minReplicas": 3}}'
or edit it manually:
$ kubectl edit hpa <hpa-name>
More information on HPAs here.
And yes, the ingress controllers are supposed to be scaled up and down depending on the load.
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
answered Nov 14 '18 at 19:00
RicoRico
27.9k94966
27.9k94966
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
add a comment |
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
This should indeed be the way to go, once i've installed a production ready nginx-ingress-controller
– RVandersteen
Nov 15 '18 at 9:12
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%2f53303411%2fscale-azure-nginx-ingress-controller%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
You probably better off installing your own ingress (you can follow this guide) and external-dns.
– alev
Nov 15 '18 at 9:32