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

fix(kuma-cp): don't run dataplane gc in global #4184

Merged
merged 1 commit into from
Apr 15, 2022

Conversation

lahabana
Copy link
Contributor

@lahabana lahabana commented Apr 15, 2022

Summary

We were running the GC in global when we should only delete dataplanes in zones.
We also moved all the conditions for setting up components inside the Setup methods to make things
easier to read.

In the future I'd like to move all the setup methods in app/kuma-cp/cmd this would avoid each package to depend on runtime also setting up the runtime has nothing to do with what the original packages do anyway

Full changelog

  • move all runtime checks inside the setup method of each component
  • make kds_zone. Callbacks not depend on runtime but directly on the map it needs.

Issues resolved

Fix #2015

@lahabana lahabana requested a review from a team as a code owner April 15, 2022 10:40
@lahabana lahabana changed the title fix(kuma-cp): don't run gc in global fix(kuma-cp): don't run dataplane gc in global Apr 15, 2022
We were running the GC in global when we should only delete dataplanes in zones.
We also moved all the conditions for setting up components inside the Setup methods to make things
easier to read

Fix kumahq#2015

Signed-off-by: Charly Molter <[email protected]>
@codecov-commenter
Copy link

Codecov Report

Merging #4184 (8d388f0) into master (16dd805) will increase coverage by 0.03%.
The diff coverage is 16.98%.

@@            Coverage Diff             @@
##           master    #4184      +/-   ##
==========================================
+ Coverage   55.85%   55.88%   +0.03%     
==========================================
  Files         930      930              
  Lines       56429    56420       -9     
==========================================
+ Hits        31516    31528      +12     
+ Misses      22401    22373      -28     
- Partials     2512     2519       +7     
Impacted Files Coverage Δ
app/kuma-cp/cmd/run.go 28.73% <0.00%> (+4.62%) ⬆️
pkg/defaults/components.go 82.14% <0.00%> (-3.05%) ⬇️
pkg/dns/components.go 70.00% <0.00%> (-7.78%) ⬇️
pkg/dp-server/components.go 33.33% <0.00%> (-16.67%) ⬇️
pkg/hds/components.go 60.00% <0.00%> (-4.29%) ⬇️
pkg/insights/components.go 83.33% <0.00%> (-16.67%) ⬇️
pkg/insights/resyncer.go 74.07% <ø> (ø)
pkg/kds/context/context.go 58.88% <0.00%> (ø)
pkg/mads/server/server.go 80.90% <0.00%> (-1.50%) ⬇️
pkg/xds/components.go 25.00% <0.00%> (-8.34%) ⬇️
... and 12 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 16dd805...8d388f0. Read the comment docs.

@lahabana lahabana merged commit 0668423 into kumahq:master Apr 15, 2022
SallyBlichWalkMe pushed a commit to SallyBlichWalkMe/kuma that referenced this pull request Apr 21, 2022
We were running the GC in global when we should only delete dataplanes in zones.
We also moved all the conditions for setting up components inside the Setup methods to make things
easier to read

Fix kumahq#2015

Signed-off-by: Charly Molter <[email protected]>
Signed-off-by: Sally Blich <[email protected]>
lukidzi pushed a commit that referenced this pull request May 11, 2022
We were running the GC in global when we should only delete dataplanes in zones.
We also moved all the conditions for setting up components inside the Setup methods to make things
easier to read

Fix #2015

Signed-off-by: Charly Molter <[email protected]>
@lahabana lahabana deleted the fix2015 branch March 29, 2024 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DP garbage-collector shouldn't be running in Global
3 participants