Multi cloud kubernetes Cluster

Kubernetes Role summary Provide frontline triage and resolution for Kubernetes cluster requests across AWS, Onprem AliCloud, and GCP. You will own tickets from intake through resolution in a Slack-based support channel, escalating to platform engineering only when a confirmed defect or capacity change is required. Singapore is the anchor site for this role, covering the APAC cluster estate at its point of origin.

Kubernetes core — must have Cluster lifecycle: create, update, delete, node pool management, stuck-state recovery Version upgrades and upgrade-failure diagnosis RBAC (Cluster

Role / RoleBinding) and its side effects on node rotation kubeconfig and kubectl troubleshooting, API server behavior and request throttling Multi-cloud — must have at least two AWS: EKS, Karpenter / EC2NodeClass, NLB and ingress-nginx, Route 53, subnet reconciliation AliCloud: ACK including region-specific Kubernetes version availability constraints GCP: GKE / GCE, vulnerability remediation workflows IS-Cloud and internal KCS control planes Platform tooling — must have Kubernetes: cluster manifests, YAML schema validation, deployment error states, CLI Observability: Prometheus, kube-state-metrics, Splunk forwarding Add-ons: Spinnaker, KEDA, Compass compliance onboarding, backup services Networking — must have Cross-environment DNS resolution and cluster-to-managed-database connectivity Load balancer reconcile loops and subnet annotation behavior Outage triage and formal RCA authorship Required Q