How to deploy to kubernetes
up vote
-1
down vote
favorite
I have a website with
a react frontend container
a node backend container
an admin panel container
a database on a separate machine
All the containers are stateless and i want to run
2 instances of frontend load balanced on domain.com,
2 instances of backend on backend.domain.com,
1 instance of admin panel on panel.domain.com
I am currently running this in docker with nginx reverse proxy to direct traffic to containers based on subdomain.
I want to move this setup to kubernetes so
My questions are
What all can be the pods in this case?
What will be the deployment here? Will there be multiple deployements?
Do I need a nginx reverse proxy to direct traffic based on sub domain to pods?
kubernetes kubernetes-ingress
add a comment |
up vote
-1
down vote
favorite
I have a website with
a react frontend container
a node backend container
an admin panel container
a database on a separate machine
All the containers are stateless and i want to run
2 instances of frontend load balanced on domain.com,
2 instances of backend on backend.domain.com,
1 instance of admin panel on panel.domain.com
I am currently running this in docker with nginx reverse proxy to direct traffic to containers based on subdomain.
I want to move this setup to kubernetes so
My questions are
What all can be the pods in this case?
What will be the deployment here? Will there be multiple deployements?
Do I need a nginx reverse proxy to direct traffic based on sub domain to pods?
kubernetes kubernetes-ingress
@user1529891 its not about stateful vs stateless. please read before marking duplicate
– Anoop Krishnan
Nov 10 at 5:04
How are you sharing state and between which containers
– Lev Kuznetsov
Nov 10 at 10:57
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have a website with
a react frontend container
a node backend container
an admin panel container
a database on a separate machine
All the containers are stateless and i want to run
2 instances of frontend load balanced on domain.com,
2 instances of backend on backend.domain.com,
1 instance of admin panel on panel.domain.com
I am currently running this in docker with nginx reverse proxy to direct traffic to containers based on subdomain.
I want to move this setup to kubernetes so
My questions are
What all can be the pods in this case?
What will be the deployment here? Will there be multiple deployements?
Do I need a nginx reverse proxy to direct traffic based on sub domain to pods?
kubernetes kubernetes-ingress
I have a website with
a react frontend container
a node backend container
an admin panel container
a database on a separate machine
All the containers are stateless and i want to run
2 instances of frontend load balanced on domain.com,
2 instances of backend on backend.domain.com,
1 instance of admin panel on panel.domain.com
I am currently running this in docker with nginx reverse proxy to direct traffic to containers based on subdomain.
I want to move this setup to kubernetes so
My questions are
What all can be the pods in this case?
What will be the deployment here? Will there be multiple deployements?
Do I need a nginx reverse proxy to direct traffic based on sub domain to pods?
kubernetes kubernetes-ingress
kubernetes kubernetes-ingress
asked Nov 10 at 4:27
Anoop Krishnan
397
397
@user1529891 its not about stateful vs stateless. please read before marking duplicate
– Anoop Krishnan
Nov 10 at 5:04
How are you sharing state and between which containers
– Lev Kuznetsov
Nov 10 at 10:57
add a comment |
@user1529891 its not about stateful vs stateless. please read before marking duplicate
– Anoop Krishnan
Nov 10 at 5:04
How are you sharing state and between which containers
– Lev Kuznetsov
Nov 10 at 10:57
@user1529891 its not about stateful vs stateless. please read before marking duplicate
– Anoop Krishnan
Nov 10 at 5:04
@user1529891 its not about stateful vs stateless. please read before marking duplicate
– Anoop Krishnan
Nov 10 at 5:04
How are you sharing state and between which containers
– Lev Kuznetsov
Nov 10 at 10:57
How are you sharing state and between which containers
– Lev Kuznetsov
Nov 10 at 10:57
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
IMO you can go with below k8s constructs
- Frontend: A deployment and service with ingress route to service
- Backend: A deployment and a service
- Admin panel: A deployment and service with ingress route to service
Pods will be taken care by deployment, and service will ensure that you can scale deployment as you will.
For ingress you can start trying out it, nginx ingress controller https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-controllers, probably load-test and try with ingress controller suits for your need.
For database I would right now, to keep in separate machine itself, don't migrate to k8s now, get comfortable with k8s for a while
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',
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%2f53235988%2fhow-to-deploy-to-kubernetes%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
up vote
0
down vote
IMO you can go with below k8s constructs
- Frontend: A deployment and service with ingress route to service
- Backend: A deployment and a service
- Admin panel: A deployment and service with ingress route to service
Pods will be taken care by deployment, and service will ensure that you can scale deployment as you will.
For ingress you can start trying out it, nginx ingress controller https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-controllers, probably load-test and try with ingress controller suits for your need.
For database I would right now, to keep in separate machine itself, don't migrate to k8s now, get comfortable with k8s for a while
add a comment |
up vote
0
down vote
IMO you can go with below k8s constructs
- Frontend: A deployment and service with ingress route to service
- Backend: A deployment and a service
- Admin panel: A deployment and service with ingress route to service
Pods will be taken care by deployment, and service will ensure that you can scale deployment as you will.
For ingress you can start trying out it, nginx ingress controller https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-controllers, probably load-test and try with ingress controller suits for your need.
For database I would right now, to keep in separate machine itself, don't migrate to k8s now, get comfortable with k8s for a while
add a comment |
up vote
0
down vote
up vote
0
down vote
IMO you can go with below k8s constructs
- Frontend: A deployment and service with ingress route to service
- Backend: A deployment and a service
- Admin panel: A deployment and service with ingress route to service
Pods will be taken care by deployment, and service will ensure that you can scale deployment as you will.
For ingress you can start trying out it, nginx ingress controller https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-controllers, probably load-test and try with ingress controller suits for your need.
For database I would right now, to keep in separate machine itself, don't migrate to k8s now, get comfortable with k8s for a while
IMO you can go with below k8s constructs
- Frontend: A deployment and service with ingress route to service
- Backend: A deployment and a service
- Admin panel: A deployment and service with ingress route to service
Pods will be taken care by deployment, and service will ensure that you can scale deployment as you will.
For ingress you can start trying out it, nginx ingress controller https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-controllers, probably load-test and try with ingress controller suits for your need.
For database I would right now, to keep in separate machine itself, don't migrate to k8s now, get comfortable with k8s for a while
answered Nov 10 at 9:20
murarisumit
5701023
5701023
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.
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%2f53235988%2fhow-to-deploy-to-kubernetes%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
@user1529891 its not about stateful vs stateless. please read before marking duplicate
– Anoop Krishnan
Nov 10 at 5:04
How are you sharing state and between which containers
– Lev Kuznetsov
Nov 10 at 10:57