Prerequisites
Get credentials for the cluster
az aks get-credentials --name templafyemailsignatureserver --resource-group <resource group>
Set kubectl context to the correct namespace
kubectl config set-context $(kubectl config current-context) --namespace=templafy-emailsignature
Actions
Update to a new Email Signature Server image:
kubectl set image deployment/email-signature-server-deployment email-signature-server=templafyprod.azurecr.io/email-signature-server:x.x.x.x --record
Rolling restart of all pods:
kubectl rollout restart deployment email-signature-server-deployment
Monitoring
Check update rollout:
kubectl rollout status deployment/email-signature-server-deployment --watch
Check rollout status:
kubectl rollout status deployment/email-signature-server-deployment
Check pods status:
kubectl get pods --watch
Check the deployed values on pods:
kubectl describe pods
Check pod resource usage:
kubectl top pod
Check pods across namespaces:
kubectl get pods --all-namespaces
Check what happened in the deployment:
kubectl describe deployments
Check the deployment history:
kubectl rollout history deployment
Get logs from all pods
kubectl logs -f -lcomponent=emailsignatureserver --all-containers=true
Rollback
Rollback to previous deployment:
kubectl rollout undo deployment/email-signature-server-deployment
1. Check the details of a deployment in the history, including environment variables:
kubectl rollout history deployment/email-signature-server-deployment --revision<$DEPLOYMENT>9
2. Rollback to that revision
kubectl rollout undo deployment/email-signature-server-deployment --to-revision=<$DEPLOYMENT>
Dashboard
Check the status on the dashboard:
az aks browse --resource-group=<resource group name> --name templafyemailsignatureserver
Comments
0 comments
Article is closed for comments.