Enable deletion of SageMaker job style CR from API server if job is complete #16
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 of Changes
Completed
,Failed
,Stopped
)Testing
Tested manually - let the job(training, process, transform & hpo) run till completion and ensured running
kubectl delete
on the CR removes the resource from management. No error on controller side.Without this PR, the controller gets stuck in backoff because of an error from SageMaker
automated tests will be part of a separate follow up of @mbaijal's PR
Related PRs
Both merged
aws-controllers-k8s/code-generator#45
aws-controllers-k8s/code-generator#26