blocks|key|1149492|text|只是为了更新到2020年-这是从规范：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1149493|MicroK8s是什么？MicroK8s是一个强大的，轻量级的，可靠的生产准备库伯奈特斯发行版.它是一个企业级的Kubernetes发行版，它具有较小的磁盘和内存占用，同时提供生产级外接插件，如Istio、disk、Grafana、纤毛等。无论您是在运行生产环境，还是对探索K8s感兴趣，MicroK8s都满足您的需要。|1149494|所以我觉得很清楚。|1149495|https://ubuntu.com/blog/introduction-to-microk8s-part-1-2|offset|length|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|1L|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@$H|T|I|U|1|V]]|A|$]]]|J|$K|$5|L|M|N|A|$O|G]]]]

just to update to 2020 - This is from canonical:

What is MicroK8s?
MicroK8s is a powerful, lightweight, reliable production-ready Kubernetes distribution. It is an enterprise grade Kubernetes distribution that has a small disk and memory footprint while offering production grade add-ons out-the-box such as Istio, Knative, Grafana, Cilium and more. Whether you are running a production environment or interested in exploring K8s, MicroK8s serves your needs.

So I think it's pretty clear.

<a href="https://ubuntu.com/blog/introduction-to-microk8s-part-1-2" rel="noreferrer">https://ubuntu.com/blog/introduction-to-microk8s-part-1-2</a>

blocks|key|1236694|text|(坦白地说，我是MicroK8s的创建者佳能公司的产品经理)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1236695|MicroK8s可用于生产。当然，生产需求各不相同，所以真正的答案是“这取决于”。|1236696|如果您有一个MicroK8s的生产用例，但是发现它缺少一个必须具备的特性，请告诉我们。您可以通过在github项目-+https://github.com/ubuntu/microk8s中提交一个问题来做到这一点。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ubuntu/microk8s^0|0|0|1N|Y|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]]]

(full disclosure, I'm a product manager at Canonical, the creators of MicroK8s)

MicroK8s can be used for production. Of course, production requirements vary, so the real answer is "it depends". 

If you have a production use case for MicroK8s but find it lacking a feature that is a must have, please let us know. You can do that by filing an issue in the github project - <a href="https://github.com/ubuntu/microk8s" rel="noreferrer">https://github.com/ubuntu/microk8s</a>.

blocks|key|1149640|text|MicroK8s是一个经认证的Kubernetes发行版，银级别，可能在云计算基础上的完整列表中发现：https://www.cncf.io/certification/software-conformance/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1149641|我会考虑生产准备好任何经认证的Kubernetes发行版，但这完全取决于您将如何使用它。|entityMap|0|LINK|mutability|MUTABLE|url|https://www.cncf.io/certification/software-conformance/^0|1F|1J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]]]

MicroK8s is a certified Kubernetes distribution, Silver level and may be discovered in the full list here on Cloud Native Computing Foundation: <a href="https://www.cncf.io/certification/software-conformance/" rel="nofollow noreferrer">https://www.cncf.io/certification/software-conformance/</a>
I would consider production ready any Kubernetes distribution which is certified, but it totally depends on how you are going to use it.

blocks|key|1149782|text|任何生产级软件都应该是“默认安全的”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1149783|在生产就绪Kubernetes解决方案(例如kubeadm)的情况下，安装到吊舱上的默认服务帐户没有任何特权。|1149784|但根据microk8s文档|offset|length|1149785|默认情况下，所有经过身份验证的请求都是在api-server使用--授权-模式=AlwaysAllow运行时授权的。|blockquote|1149786|这意味着，默认情况下没有授权。这将允许任何服务帐户(包括默认帐户)调用并执行特权操作(例如，在kube-system命名空间中创建和读取秘密)。由于不存在RBAC，默认服务帐户将在集群上具有群集管理权限。这对于开发环境来说很好，但在生产中可能是相当危险的。|1149787|假设在pod中运行的应用程序容易受到远程代码执行等问题的影响。它将有可能从吊舱中挣脱出来，破坏整个集群。|1149788|可以使用microk8s+enable+rbac启用RBAC。|style|CODE|1149789|缺少这样的设置可能会导致配置错误的集群和几个问题。因此，建议使用发行版(或一般任何软件)。|entityMap|0|LINK|mutability|MUTABLE|url|https://microk8s.io/docs/services-and-ports^0|0|0|3|A|0|0|0|0|0|4|K|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@$F|14|G|15|1|16]]|A|$]]|$1|H|3|I|5|J|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1A|8|@$F|1B|G|1C|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

Any production grade software should be &quot;secure by default&quot;.
In case of production ready Kubernetes solutions (e.g. kubeadm), the default service account which is mounted to the pod does not have any privilege.
But as per the <a href="https://microk8s.io/docs/services-and-ports" rel="nofollow noreferrer">microk8s documentation</a>
<blockquote>
By default all authenticated requests are authorized as the api-server runs with --authorization-mode=AlwaysAllow.
</blockquote>
It means, by default there is no authorization. This will allow any service account (including default) to invoke the kube-apiserver and perform privileged operations (e.g. creating and reading secrets in kube-system namespace). The default service account will have cluster admin privilege on the cluster since there is no RBAC. This is fine for the development environment, but it can be quite dangerous in production.
Suppose an application running inside a pod is vulnerable to issues like remote code execution. It will be possible to break out from the pod and compromise the complete cluster.
RBAC can be enabled using <code>microk8s enable rbac</code>.
Missing such settings might result in misconfigured cluster and several issues down the line. So it is recommended to use the production ready Kubernetes distribution (or in general any software).

blocks|key|1149381|text|正如评论中提到的，我最终遇到了一些地方，他们说microk8s只用于开发：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1149382|https://kubernetes.io/docs/setup/pick-right-solution/+-+"microk8s在本地机器上为开发和测试提供了最新Kubernetes发行版的单一命令安装。|offset|length|1149383|https://blog.ubuntu.com/2018/08/13/deploying-kubernetes-on-public-clouds-is-hard-or-is-it+--“如果您开发的软件是为在Kubernetes上运行而设计的，那么microk8s+snap提供了最简单的方法，可以在您的笔记本电脑或虚拟机上在30秒内启动并运行一个完全一致的本地Kubernetes，以便进行测试和软件开发。”|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/setup/pick-right-solution/|1|https://blog.ubuntu.com/2018/08/13/deploying-kubernetes-on-public-clouds-is-hard-or-is-it^0|0|0|1H|0|0|0|2H|1^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]|O|$5|J|K|L|A|$M|P]]]]

As mentioned in the comments, I eventually came across a couple of places where they say microk8s is only for development:

<a href="https://kubernetes.io/docs/setup/pick-right-solution/" rel="nofollow noreferrer">https://kubernetes.io/docs/setup/pick-right-solution/</a> - "microk8s provides a single command installation of the latest Kubernetes release on a local machine for development and testing."

<a href="https://blog.ubuntu.com/2018/08/13/deploying-kubernetes-on-public-clouds-is-hard-or-is-it" rel="nofollow noreferrer">https://blog.ubuntu.com/2018/08/13/deploying-kubernetes-on-public-clouds-is-hard-or-is-it</a> - "If you develop software designed to run on Kubernetes, the microk8s snap provides the easiest way to get a fully conformant local Kubernetes up and running in under 30 seconds on your laptop or virtual machine for test and software development purposes."

<a href="https://github.com/ubuntu/microk8s" rel="noreferrer">microk8s</a> appears to be an easy way to install Kubernetes on Ubuntu. Several places refer to it as an alternative to minikube, which is not aimed at production environments, and <a href="https://discuss.kubernetes.io/t/microk8s-a-lightweight-locally-install-kubernetes/463/6" rel="noreferrer">this post</a> seems to indicate that it's mostly aimed at development environments. However, I don't see a reason why it's not suitable for production environments.

I have two Ubuntu servers and want to install Kubernetes on each while maintaining the legacy applications that also run on these servers. I'm wondering if microk8s is a good choice for this scenario.

Is microk8s suitable for production environments, or is it just for development?

Is microk8s suitable for production environments, or is it just for development?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

microk8s似乎是在Ubuntu上安装Kubernetes的一种简单方法。有几个地方称其为minikube的替代品，后者不是针对生产环境的，这个职位似乎表明它主要针对开发环境。但是，我看不出为什么它不适合生产环境。我有两个Ubuntu服务器，希望在每个服务器上安装Kubernetes，同时维护运行在这些服务器上的遗留应用程序。我在想，对于这种情况，microk8s是否是一个好选择。microk

问microk8s是否适合于生产环境，还是只适用于开发？
EN

回答 5

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问microk8s是否适合于生产环境，还是只适用于开发？EN

回答 5

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问microk8s是否适合于生产环境，还是只适用于开发？
EN