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

Refactor SKR watcher installation to use native Kubernetes client #313

Merged
merged 120 commits into from
Jan 23, 2023
Merged

Refactor SKR watcher installation to use native Kubernetes client #313

merged 120 commits into from
Jan 23, 2023

Conversation

fourthisle
Copy link
Contributor

@fourthisle fourthisle commented Nov 15, 2022

implementation of #301

fourthisle and others added 30 commits October 18, 2022 19:17
…o watcher-reconciles-kymas

# Conflicts:
#	operator/internal/deploy/chart_manager.go
@fourthisle fourthisle changed the title WIP-Refactor SKR watcher installation to use native Kubernetes client Refactor SKR watcher installation to use native Kubernetes client Jan 16, 2023
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 16, 2023
@fourthisle fourthisle changed the title Refactor SKR watcher installation to use native Kubernetes client WIP-Refactor SKR watcher installation to use native Kubernetes client Jan 16, 2023
@fourthisle
Copy link
Contributor Author

/test pull-lifecycle-mgr-tests

@fourthisle fourthisle changed the title WIP-Refactor SKR watcher installation to use native Kubernetes client Refactor SKR watcher installation to use native Kubernetes client Jan 20, 2023
Copy link
Contributor

@jakobmoellerdev jakobmoellerdev left a comment

Choose a reason for hiding this comment

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

LGTM, good stuff! waiting for other reviews

return true, err
}
for _, resource := range resources {
err := syncContext.RuntimeClient.Patch(ctx, resource, client.Apply, client.ForceOwnership, skrChartFieldOwner)
Copy link
Contributor

Choose a reason for hiding this comment

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

would you kindly update this to a concurrent implementation using ErrGroup? otherwise we will have to wait for each resource patch to complete, which develops bottlenecking here

Comment on lines 101 to 104
if err := syncContext.RuntimeClient.Delete(ctx, resource); err != nil && !apierrors.IsNotFound(err) {
return fmt.Errorf("failed to delete webhook %s: %w", resource.GetKind(), err)
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

does it make sense to implement similar errGrp here, so that deletion of following resources are not blocked by one failing?

@kyma-bot kyma-bot added the lgtm Looks good to me! label Jan 23, 2023
@kyma-bot kyma-bot merged commit 4643b27 into kyma-project:main Jan 23, 2023
jakobmoellerdev added a commit to jakobmoellerdev/kyma-operator that referenced this pull request Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Looks good to me! size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants