Skip to content

Conversation

xrstf
Copy link
Contributor

@xrstf xrstf commented Jun 11, 2025

Summary

This PR refactors the agent to make use of multicluster-runtime and the apiexport provider from multicluster-provider.

Notably, since kube clients do not use the context anymore to switch between clusters, many functions in the syncer now have a dedicated singular ctx parameter that is used for all kube interactions on both sides of the sync.

The e2e tests make use of the ClusterClient in multicluster-runtime to still be scopable down to a specific workspace (but not by setting a context anymore, but by calling .Cluster(<name>)).

Even though the agent is now based on 0.28, it still tests against 0.27 because we found kcp-dev/kcp#3527 during testing (and there are more slight adjustments that we'd need to make to support 0.28).

What Type of PR Is This?

/kind feature

Release Notes

Refactor agent to work based on multicluster-runtime.

/hold

This must not be merged before kcp 0.28 is released.

@kcp-ci-bot kcp-ci-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Indicates the PR's author has signed the DCO. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 11, 2025
@xrstf xrstf changed the title refator agent to use multicluster-runtime refactor agent to use multicluster-runtime Jun 11, 2025
@kcp-ci-bot kcp-ci-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 18, 2025
@kcp-ci-bot kcp-ci-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 11, 2025
@xrstf
Copy link
Contributor Author

xrstf commented Aug 11, 2025

/unhold

@kcp-ci-bot kcp-ci-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 11, 2025
@xrstf xrstf requested a review from embik August 12, 2025 12:17
Copy link
Member

@embik embik left a comment

Choose a reason for hiding this comment

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

/approve

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2025
@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d615f19068e45a660571b409149b461952bb456c

@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2025
@kcp-ci-bot kcp-ci-bot merged commit 97f4068 into main Aug 26, 2025
9 checks passed
@kcp-ci-bot kcp-ci-bot deleted the multicluster branch August 26, 2025 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. 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.

3 participants