blocks|key|114353|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|-4|4|5|6|B|7|@]|8|@]|9|$]]]|A|$]]

AKS, EKS and GKE are so called managed kubernetes solutions. Their goal and functionality is basically the same. There are of course some differences, especially on how such managed kubernetes cluster can be integrated with the rest of the specific cloud platform but all the vendors do their best to make sure it is in no way inferior to the competition.
<blockquote>
why AKS,EKS,GKE better than k8s .can we say k8s architecture is base
of these 3. How they leverage each other?
</blockquote>
Are they ? I wouldn't say they are better, they are simply different. The ultimate evaluation what is actually better depends entirely on your specific needs and requirements.
Yes, those 3 solutions are entirely based on open source kubernetes with some additional modifications and improvements developed separately by each cloud provider. You can read more about kubernetes history in this <a href="https://en.wikipedia.org/wiki/Kubernetes" rel="nofollow noreferrer">Wikipedia article</a>. In short, it was originally developed by Google based on their experiences with their internal system for container orchestration called Borg and subsequently released as an open-source technology:
<blockquote>
Kubernetes v1.0 was released on July 21,
2015.<a href="https://en.wikipedia.org/wiki/Kubernetes#cite_note-13" rel="nofollow noreferrer">[13]</a> Along with the Kubernetes v1.0 release, Google partnered with the
<a href="https://en.wikipedia.org/wiki/Linux_Foundation" rel="nofollow noreferrer" title="Linux Foundation">Linux Foundation</a> to form the <a href="https://en.wikipedia.org/wiki/Cloud_Native_Computing_Foundation" rel="nofollow noreferrer" title="Cloud Native Computing Foundation">Cloud Native Computing
Foundation</a>
(CNCF)<a href="https://en.wikipedia.org/wiki/Kubernetes#cite_note-14" rel="nofollow noreferrer">[14]</a>
and offered Kubernetes as a seed technology.
</blockquote>
To set up your kubernetes cluster on your own you have tools like <a href="https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/" rel="nofollow noreferrer">kubeadm</a> which simplifies the whole process but still gives you full control of your kubernetes environment. But it has both advantages and disatvantages. From one hand you have complete control over your master node, but from the other you are the one who is fully responsible for administering such environment and if something goes wrong e.g. with your production cluster, you are the one who needs to fix it.
Some users need even more granular level of control both over the cluster setup process as well as its administration. You've probably heard of the approach to setting up your kubernetes cluster 100% manually. It's called <a href="https://github.com/kelseyhightower/kubernetes-the-hard-way" rel="nofollow noreferrer">kubernetes the hard way</a>. If you went through it at least once, you probably know how complicated and tedious process it can be.
Unlike the two above, managed kubernetes environments totally take this burden off you and the working kubernetes cluster that doesn't require any further configuration can be set up completely automatically in a few minutes.
Advantages of such solution ? Well, with no doubts there are many. Less administration effort, less energy and time you need to dedicate to set up and manage kubernetes cluster itself and you can focus mainly on deploying and managing the workload. Every benefit involves however some trade-offs and also here by choosing one of managed kubernetes solutions you give up full control of your environment. Keep in mind that GKE, AKS and AKS don't give you access to master node. So if you want to reconfigure your kube-apiserver or other element of the cluster by running it with some completely different <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/#options" rel="nofollow noreferrer">flag</a>, you're not allowed to do that. In exchange you don't care if the whole master node goes down as it is your cloud provider's responsibility to manage it properly for you.
So as I've already said, it entirely depends on your particular needs and expectations. You can ask the same way: &quot;Why to use the cloud, IaaS, PaaS, SaaS if we can manage our infrastructure on our own ? There are so many datacenters that allow you to place your physical servers, so why to bother with some cloud solutions ?&quot; - But you would probably agree that using cloud has many advantages. It provides unprecedented level of scalability and elasticity and high availability, to name just a few but you probably know that this list is very long.
<blockquote>
In the cloud, Can we do container orchestration without the above
services means can we have compute instances like ec2/VM and install
k8s (open source project) on those nodes, which means make our own k8s
cluster?
</blockquote>
Of course w can. You can set up your own kubernetes environment with full access to master node on GCP Compute Engine VMs but as I said, it requires more administration effort. You can set up your kubernetes cluster on virtual machines in the cloud, the same way as you would do this on-prem.
<blockquote>
If yes, How we can add more nodes automatically to a cluster if any
node goes down?
</blockquote>
Well, you can always develop your own solution to automate this process, but in generall if you set up your kubernetes cluster manually, the answer is: you can't. This is also one great advantage of managed kubernetes solutions as pure open source kubernetes simply doesn't havy such features and won't automatically spawn an additional node when one of them goes down. Actually it isn't even designed for such purpuse and it works on a different level. It's about managing containers running our workload, not about managing cloud infrastructure.
Take a look at <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/kubernetes-engine-overview" rel="nofollow noreferrer">this</a> article where you have a basic overview of Google Kubernetes Engine including the advantages of GKE over pure open source kubernetes:
<blockquote>
<h3>Kubernetes on Google Cloud</h3>
When you run a GKE cluster, you also gain the benefit of advanced
cluster management features that Google Cloud provides. These include:
<ul>
<li>Google Cloud's <a href="https://cloud.google.com/compute/docs/load-balancing-and-autoscaling" rel="nofollow noreferrer">load-balancing</a>
for Compute Engine instances</li>
<li><a href="https://cloud.google.com/kubernetes-engine/docs/concepts/node-pools" rel="nofollow noreferrer">Node pools</a>
to designate subsets of nodes within a cluster for additional
flexibility</li>
<li><a href="https://cloud.google.com/kubernetes-engine/docs/cluster-autoscaler" rel="nofollow noreferrer">Automatic scaling</a>
of your cluster's node instance count</li>
<li><a href="https://cloud.google.com/kubernetes-engine/docs/concepts/node-auto-upgrades" rel="nofollow noreferrer">Automatic upgrades</a>
for your cluster's node software</li>
<li><a href="https://cloud.google.com/kubernetes-engine/docs/concepts/node-auto-repair" rel="nofollow noreferrer">Node auto-repair</a>
to maintain node health and availability</li>
<li><a href="https://cloud.google.com/monitoring/kubernetes-engine" rel="nofollow noreferrer">Logging and monitoring</a>
with Google Cloud's operations suite for visibility into your cluster</li>
</ul>
</blockquote>
As to:
<blockquote>
If no, why people compare k8s vs EKS vs aks vs gke as k8s should not
be part of that?
</blockquote>
For comparing EKS vs AKS vs GKE there is a simple reason. Behind every of them stands another big player and they are simply competitive solutions attempting to be one step ahead from the competition, which basically is also very positive as it additionally drives their intensive development.
Comparing each of them separately with open source k8s also makes a perfect sense as for some uses it might be better to consider setting up our own k8s cluster from scratch and have very granular control over each detail e.g. setting the specific flags kube-apiserver or kube-scheduler is started with etc.
<blockquote>
At few places I found, people said it's like plain Hadoop and Cloudera
Hadoop (fully manages Hadoop cluster which makes life easy and adds
value to the table).
</blockquote>
yes, this is a very accurate comparison. Keep in mind that setting up a complex cluster, consisting of many elements is much more complicated than installing a simple http or database server (but you also can find hosting providers that make your life easier and offer fully managed solutions). Even if they consist of a few replicas, usually their setup requires less time and energy than setting up a cluster consisting of many related elements, where one heavily depends on another. If you take a closer look at <a href="https://kubernetes.io/docs/concepts/overview/components/" rel="nofollow noreferrer">those elements</a> in kubernetes you'll find out that it's not such a homogenous environment and although when you set everything up automatically it may seem as such, in fact it isn't.
I hope this shed some light on your understanding of kubernetes and in particular the sense of using kubernetes managed solutions.

I am trying to learn k8s, and 1 question always coming as to why we need GKE, aks, or EKS.
In the cloud, Can we do container orchestration without the above services means can we have compute instances like ec2/VM and install k8s (open source project) on those nodes, which means make our own k8s cluster? If yes, How we can add more nodes automatically to a cluster if any node goes down? where we can challenges if we do that way? what features do we miss in this approach?
If no, why people compare k8s vs EKS vs aks vs gke as k8s should not be part of that?
At few places I found, people said it's like plain Hadoop and Cloudera Hadoop (fully manages Hadoop cluster which makes life easy and adds value to the table).
I know all these services make job lot easier but nowhere I find that this is also one way of doing though it is very very complex setting up your own cluster with multiple nodes.
Any good content where I can find a reason why not only k8s.
At many places, people compared k8s with EKS,gke and AKS and shown k8s is best but nowhere I find in use case k8s is implemented without these services.
Also at many places, I see k8s is not good but still it's sidely used everywhere why so and how it is better than eks,gke and aks?

why AKS,EKS,GKE better than k8s .can we say k8s architecture is base of these 3. How they leverage each other?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在努力学习k8s，一个问题总是来问为什么我们需要GKE，as，或者EKS。在云中，我们可以在没有上述服务的情况下进行容器编排吗?我们是否可以在这些节点上进行计算实例(如ec2/VM )和安装k8s (开放源码项目)，这意味着我们可以创建自己的k8s集群？如果是，如果任何节点发生故障，我们如何能够自动向集群中添加更多节点？如果我们这样做，我们能在哪里挑战呢？在这种方法中，我们忽略了哪些特性？如果

问为什么AKS，EKS，GKE比k8s .can更好，我们说k8s体系结构是这3种体系结构的基础。
EN

回答 1

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么AKS，EKS，GKE比k8s .can更好，我们说k8s体系结构是这3种体系结构的基础。EN