Update coredns to execute a rollout when no patch is required. #224
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
Fixes #223
This PR adds a deployment rollout when a patch isn't required for coredns. This is necessary to ensure coredns is scheduled on Fargate when a patch operation doesn't take place. Without the update the coredns deployment will remain in the pending state.
Documentation
TODOs
Read the Gruntwork contribution guidelines.
Please ensure all of these TODOs are completed before asking for a review.
feature/new-vpc-endpoints-955
orbug/missing-count-param-434
.Release Notes (draft)
schedule coredns
to perform a rollout when patch operation isn't executed for scheduling coredns on Fargate.Migration Guide