Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle scaling down deployments #13

Merged
merged 2 commits into from
Jul 21, 2021

Conversation

laverya
Copy link
Member

@laverya laverya commented Jul 21, 2021

No description provided.

@laverya laverya requested a review from emosbaugh July 21, 2021 00:54
return fmt.Errorf("expected 1 owner for replicaset %s in %s, found %d instead", ownerName, ns, len(rs.OwnerReferences))
}
if rs.OwnerReferences[0].Kind != "Deployment" {
return fmt.Errorf("expected owner for replicaset %s in %s to be a deployment, found %s of kind %s instead", ownerName, ns, rs.OwnerReferences[0].Name, rs.OwnerReferences[0].Kind)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can nothing else own replica sets?

Copy link
Member Author

@laverya laverya Jul 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not that I've seen in apps/v1 (not daemonsets or statefulsets, possibly jobs)

this still improves the situation though (from just statefulsets to also deployments)

@laverya laverya merged commit 7f6e942 into main Jul 21, 2021
@laverya laverya deleted the laverya/handle-scaling-down-deployments branch July 21, 2021 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants