Cluster management coordinates Kubernetes environments across cloud and on-premises deployments. Anthos adds a consolidated console, common service mesh, configuration management, and shared support path while retaining upstream Kubernetes capabilities. section 3.1.3
Operational responsibilities include:
- Registering clusters and authenticating access so administrators can inspect Pods, Services, ConfigMaps, persistent volumes, and workloads. section 5.1.3
- Connecting through Google Cloud console, Google Cloud Shell, kubectl, or the Connect gateway for remote operations. section 5.1.3
- Editing and applying YAML, inspecting node conditions, and cordoning or draining nodes during fault investigation. section 5.1.3
- Operating workloads across clusters while automating management and scripting procedures for sound SRE practice. section 5.1.3
- Upgrading, scaling, monitoring, logging, and designing operations procedures across hybrid Anthos environments. section 5.7
Emergency YAML change
An administrator can select a cluster in Google Cloud console, connect through the generated Cloud Shell command, and edit a YAML deployment without directly using kubectl. Because the action becomes a Kubernetes API or kubectl edit operation through the Connect Agent, console editing belongs mainly in triage or development rather than production. section 5.1.3
