pinniped pods are in crashloop state
search cancel

pinniped pods are in crashloop state

book

Article ID: 419951

calendar_today

Updated On:

Products

VMware Tanzu Kubernetes Grid Management

Issue/Introduction

  • goreplicaset pinniped-concierge/pinniped-concierge is missing owner

Environment

2.5.4

Cause

A stale or orphaned ReplicaSet exists for the pinniped-concierge application that is missing the required ownerReferences metadata linking it back to the parent Deployment.

Resolution

  1. Create a backup of the current deployment configuration.
    kubectl get deployment -n pinniped-concierge pinniped-concierge -o yaml > pinniped-concierge-deployment-backup.yaml

  2. Scale Down the Deployment
    kubectl scale deployment pinniped-concierge --replicas=0 -n pinniped-concierge

  3. Check the status of the new Pods and ReplicaSets
    kubectl get pods -n pinniped-concierge
    kubectl get rs -n pinniped-concierge
  4. Clean Up Old ReplicaSets
    kubectl delete rs <old-rs-name> -n pinniped-concierge

  5. Scale Up the Deployment
    kubectl scale deployment pinniped-concierge --replicas=2 -n pinniped-concierge