Logs scrolled by. No errors. Just slow database queries. Frustrated, she patched the deployment to increase the number of replicas.
She wasn't in . She was in staging-cluster . kubectl get-contexts
The specific backend cluster and user credentials associated with that name. Logs scrolled by
$ kubectl config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE * dev-cluster development dev-user frontend - prod-cluster production admin-user - test-rig test-cluster test-user testing kubectl get-contexts
The terminal confirmed the scale. But the latency didn't budge.
A context in the config file looks like this:
kubectl config use-context prod-cluster kubectl get-contexts CURRENT NAME CLUSTER dev-cluster dev-cluster staging-cluster staging-cluster * prod-cluster prod-cluster