Clean up pal-enterprises stale ReplicaSets + CreateContainerConfigError pod #371
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform#371
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
Standalone — discovered during platform health audit 2026-05-18.
Repo
ldraney/pal-e-platformWhat Broke
pal-enterprises has a stuck pod (
pal-enterprises-94c89dc5c-hgjvh) in CreateContainerConfigError for 6+ days. Pod references env vars from secretpal-enterprises-secretswhich is missing or incomplete. Service is healthy on a newer RS (5747957c7b, 1/1 Running) usingrails-envsecret. 12 total ReplicaSets, 10 scaled to 0 and stale (7-9 days old).Repro Steps
kubectl get pods -n pal-enterprises— observe CreateContainerConfigError podkubectl get rs -n pal-enterprises— observe 10 stale ReplicaSets at 0 desiredkubectl get secret pal-enterprises-secrets -n pal-enterprises— check if secret existsExpected Behavior
Only healthy ReplicaSets should exist. Failed rollouts should be cleaned up.
Environment
Acceptance Criteria
pal-enterprises-94c89dc5c-hgjvhdeleted5747957c7b) remains Runningpal-enterprises-secretssecret deleted if it existsRelated
project-pal-e-platform— platform health