Support Argo Rollout controller object as a first class citizen #241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Initially, we naively thought that if a pod is managed by a replicaset, then that replicaset is managed by a deployment object.
This is no longer the case, since objects like Argo Rollouts are also leveraging the replicaset objects to handle pods.
This PR adds support for Argo Rollout controller object as a first class citizen in shredder, and adjust their
spec.restartAt
filed setting when a rollout restart is identified as needed by k8s-shredder. See https://argo-rollouts.readthedocs.io/en/stable/features/restart/#restarting-rollout-pods for more details.Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: