简体   繁体   English

GKE Autopilot 集群未在 UI 中显示任何内容

[英]GKE Autopilot Cluster Not Displaying Anything in UI

I have a Kubernetes cluster on GKE Autopilot that works in every way: I can view everything with kubectl in the cloud terminal and my application is successfully running as expected.我在 GKE Autopilot 上有一个 Kubernetes 集群,它可以在各个方面工作:我可以在云终端中使用 kubectl 查看所有内容,并且我的应用程序按预期成功运行。 The issue is there is just about no UI on the Google Cloud Platform.问题是谷歌云平台上几乎没有用户界面。 I can't see any workloads, ingress, or container logs despite being able to view the resources with kubectl.尽管能够使用 kubectl 查看资源,但我看不到任何工作负载、入口或容器日志。 I just moved my cluster from a standard GKE cluster (where the UI worked) to an autopilot GKE cluster, am I doing something wrong?我刚刚将我的集群从标准 GKE 集群(UI 工作的地方)移到了 Autopilot GKE 集群,我做错了什么吗? Shouldn't GKE be able to automatically pick up resources and display them in the UI? GKE 不应该能够自动拾取资源并在 UI 中显示它们吗?

Autopilot is a new mode of operation in Google Kubernetes Engine (GKE) that is designed to reduce the operational cost of managing clusters, optimize your clusters for production, and yield higher workload availability. Autopilot 是 Google Kubernetes Engine (GKE) 中的一种新操作模式,旨在降低管理集群的运营成本、针对生产优化集群并产生更高的工作负载可用性。 The mode of operation refers to the level of flexibility, responsibility, and control that you have over your cluster.操作模式是指您对集群的灵活性、责任和控制级别。 With Autopilot all node management operations are eliminated.使用 Autopilot 消除了所有节点管理操作。 This maximizes your cluster efficiency and helps to provide a stronger security posture.这可以最大限度地提高集群效率,并有助于提供更强大的安全态势。

With Autopilot, you no longer have to monitor the health of your nodes or calculate the amount of compute capacity that your workloads require.使用 Autopilot,您不再需要监控节点的运行状况或计算工作负载所需的计算容量。 Autopilot supports most Kubernetes APIs, tools, and its rich ecosystem. Autopilot 支持大多数 Kubernetes API、工具及其丰富的生态系统。 You stay within GKE without having to interact with the Compute Engine APIs, CLIs, or UI, as the nodes are not accessible through Compute Engine, like they are in Standard mode.您留在 GKE 中而无需与 Compute Engine API、CLI 或 UI 交互,因为节点无法通过 Compute Engine 访问,就像它们处于标准模式一样。 You pay only for the CPU, memory, and storage that your Pods request while they are running.您只需为 Pod 运行时请求的 CPU、内存和存储付费。

Using Autopilot, GKE provisions and manages the cluster's underlying infrastructure, including nodes and node pools, giving you an optimized cluster with a hands-off experience. GKE 使用 Autopilot 预配和管理集群的底层基础架构,包括节点和节点池,为您提供无需干预的优化集群。

As indicated, GKE fully manages nodes and node pools in the Autopilot mode.如上所述,GKE 在 Autopilot 模式下完全管理节点和节点池。 Therefore, nodes are not accessible through Compute Engine, like they are in Standard mode.因此,节点无法通过 Compute Engine 访问,就像它们处于标准模式一样。

Note : Converting Standard clusters to Autopilot mode and converting Autopilot clusters to Standard mode is not supported.注意:不支持将标准集群转换为 Autopilot 模式和将 Autopilot 集群转换为标准模式。

Refer Autopilot Overview for information.有关信息,请参阅自动舵概述

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM