Is k8s a good idea to run a simple application? [closed] - docker

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I am tring to use Docker to hold my blog website. But before coding, I know the k8s from the web.
I am totally green with web, so it confused me that is it a good idea to hold my blog in k8s? The infometion from web tell me that k8s > Docker. I do not know is it a really a good idea or not? I have try to learn the k8s for 2 days, and know what is the cluster, services and pods and so on. But it sound not make my work easy...
Should I go on to learn the k8s or it is just a bad idea and I should turn around to just learn how to learn Docker?
Thanks.

It depends on your need for high availability and performance for your blog and how many machines you are willing to use to host your blog.
What I read from your "new-ness" to the web you do not need to go there yet. Docker is probably enough for.
First get familiar with docker / containers and then with K8S.
If you also want to learn Docker this might be a good resource (https://docker-from-scratch.ivonet.nl/) ... shameless plug 😄

Related

Why do we need Docker? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 12 months ago.
Improve this question
I need a detailed answer to explain
importance of docker
need of Docker , why are we using docker
how Docker plays an important role in the field of development and Deployment .
Top benefits are:
isolation of the environment
easy to test out new software/technologies without any effort to install them
deployments are very fast
integrates great with the concept of micro services
popularity
there is a lot of useful images, that can be used, by a lot of companies
There is also a lot of good articles, that you can find, when you type something like "docker biggest benefits" in google.

Docker Swarm security best practice [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I am trying to create my docker swarm environment and my goal is to have all the best security practice related to docker swarm.
I am not really able to find everything I want about swarm security on topics like :
Authentification,
Encryption,
Users and Groups,
Files permission,
Logs,
Among others.
Do any of you have nice ressources where I can find all the information ?
Thanks in advance
Docker swarm is just an orchestration tool, in order to get a secure cluster running you just need to follow the best practices regarding Docker itself (for example, do not run containers as root user).
Check out docker secrets https://docs.docker.com/engine/swarm/secrets/ to keep secrets out of the config yaml files.
You've asked a very broad question and most of the things you mentioned are dependant on the application running in Docker.

Should I use Serverless or Kubernetes or Docker Swarm? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
We have a product that each device will report data to our server every minute, we've sold 10K and it'll be more than 100K within the next 2 years.
Now, we just use AWS EC2(8 CPUs) + Nginx + Koa2, there're 8 instances, according to the requirement increasing, it won't be appropriate anymore.
So, I'm confused about which one should I choose?
BTW, I've been using AWS Lambda for 2 years to develop IOT issues and I used Docker 5 years ago, I think all of these three ways can solve my issue.
Kubernetes is a great tool if you are not sure how your application is going to scale out. Using Amazon's Kubernetes engine or GCP equivalent Kubernetes engine can help you create and manage these clusters with click of few buttons and manage your application containers using Kubernetes's superior container orchestration framework.
Docker swarm , IMO , has lost to kubernetes because they did not seem to have jumped into this part of architecture soon enough and kubernetes has already created a very mature framework with great adoption in many production environments and lot of community support for any issues related to it.
Another advantage of using an Orchestration mechanism instead of AWS native services would be that you do not get into Vendor lock-in situations and you can move your stack to any other cloud platform hosting Kubernetes easily.
If you are also interested in continue to use your Serverless architecture , you might want to look at Open FAAS which can be leverage on top of your Kubernetes framework. Check this link for more details.

Puppet & Docker [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I was going through Puppet and comparing it with Docker.
I came to know that Puppet is used for configuration management for scalable infrastructure. New VM's setup can be done with same configuration easily etc.
Seems that Docker is also capable of all these though in a different way.
Is docker replacing the configuration management tools like puppet, chef etc?
Please help me to understand.
Thanks in advance.
Unsure of if this question belongs here or not, but never the less, here is some source material that probable explains it better than me: http://cloudify.co/2014/10/30/Docker-cloud-orchestration-configuration-management.html
Docker operates in a different manner than Chef or Puppet. Docker is (with limited exceptions) a static system. Chef et. al. are dynamic in nature. If you seek to change a fleet of Docker provisioned services you would create a new Docker container, push it out and blow away your old ones.
Chef et. al. instead check frequently for state changes and when they occur they pull those changes down and converge. This leaves room for having parts of the server automated and some not (if its a difficult to manage portion, for instance, or for emergency repairs).
Of the two Docker is the stronger model in my opinion but even then you should have some well defined CM to create your docker images, such as serverless Chef, Ansible or other.

OpenShift V3 vs. OpenShift V2 [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm searching for a main difference between OpenShift V3 and V2.
Is OpenShift V2 working like this?: https://www.openshift.com/walkthrough/how-it-works
And how are Docker and Kubernetes working in V3?
Can someone give me a clear explanation about the build-up of OpenShift V2 and V3
This is a rather broadly asked question, so I will (and can) answer only in a rather broad manner.
There are a lot of key concepts that have changed. These are the most important ones and you'll need some time to get into it, but they are a big improvement to OpenShift v2.:
Cartridges vs. Docker Containers
Gears vs. Kubernetes Pods
Broker vs. Kubernetes Master
Release of Red Hat Enterprise Linux Atomic
Host
When you'll study the links below you will understand, that (really exaggerated) OpenShift v3 has basically nothing to do with v2 besides the name, the logo and the PaaS focus. But it's still a great tool and IMO has set new standards in the PaaS-world. (No, I don't work for RedHat ;)
What's New:
https://docs.openshift.com/enterprise/3.0/whats_new/overview.html
https://docs.openshift.com/enterprise/3.0/architecture/overview.html
For starters; Docker & Kubernetes:
https://blog.openshift.com/openshift-v3-platform-combines-docker-kubernetes-atomic-and-more/
Pretty new:
Creating a Kubernetes Cluster to Run Docker Formatted Container Images
EDIT 2016_06_30:
Sorry for necro'ing this old post, but I wanted to add this quick, fun and very informative video about Kubernetes: https://youtu.be/4ht22ReBjno

Resources