Cleanup droplets on kpack.Build
deletion
#2284
Merged
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.
Is there a related GitHub Issue?
#2229
What is this change about?
Korifi now reconciles kpack.Build resources with the
korifi.cloudfoundry.org/build-workload-name
label set, i.e. those managed by korifi.It adds a finalizer that when triggered deletes the associated droplet image, if any, from the container registry.
As an associated refactor, we have used the same registry client library in the buildworkload reconciler to fetch image process details.
Does this PR introduce a breaking change?
No
Acceptance Steps
Push an app. Delete it. See the droplet images are removed from the container registry.
Tag your pair, your PM, and/or team
@gcapizzi