Skip to content

Add support for service annotation propagation #1457

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

Merged

Conversation

silvery1622
Copy link
Contributor

What this PR does / why we need it:
Enable propagation of Service annotations from workload clusters to influence final Service creation.
Only propagates annotations when enable-service-annotation-propagation is explicitly set true.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Release note:

    Service Annotation Propagation: Annotations defined in workload clusters can now be propagated to dynamically influence Service resource creation.
    This feature is ​opt-in and requires explicit enablement. Set enable-service-annotation-propagation=true to activate annotation propagation.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 28, 2025
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 28, 2025
@silvery1622 silvery1622 marked this pull request as draft March 28, 2025 07:41
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 28, 2025
@silvery1622 silvery1622 marked this pull request as ready for review March 28, 2025 07:42
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 28, 2025
@silvery1622
Copy link
Contributor Author

/retest-required

@silvery1622 silvery1622 force-pushed the service-annotation-propagation branch 2 times, most recently from c1ededd to d0743f1 Compare March 28, 2025 08:49
@silvery1622
Copy link
Contributor Author

silvery1622 commented Mar 28, 2025

E2E test passed: team-cluster-api#83

Copy link
Collaborator

@zhanggbj zhanggbj left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution!
/lgtm
/approve
/hold for other reviewers to take a review
CC @lubronzhan I assume this only impact the paravirtual mode, just tag you for awareness and review.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 31, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 31, 2025
@silvery1622
Copy link
Contributor Author

@DanielXiao Could you also review this PR when you have a chance? Thanks!

@silvery1622 silvery1622 requested a review from zhanggbj April 2, 2025 06:23
Enable propagation of Service annotations from workload clusters
to influence final Service creation.
Only propagates annotations when enable-service-annotation-propagation
is explicitly set true.
@silvery1622 silvery1622 force-pushed the service-annotation-propagation branch from d0743f1 to 9586e38 Compare April 7, 2025 03:06
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 7, 2025
@DanielXiao
Copy link
Collaborator

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 8, 2025
@zhanggbj
Copy link
Collaborator

zhanggbj commented Apr 8, 2025

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DanielXiao, silvery1622, zhanggbj

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:
  • OWNERS [DanielXiao,silvery1622,zhanggbj]

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

@zhanggbj
Copy link
Collaborator

zhanggbj commented Apr 8, 2025

/unhold
Thanks for the PR. Let's merge it.

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 8, 2025
@zhanggbj zhanggbj merged commit 28cdaad into kubernetes:master Apr 8, 2025
13 of 14 checks passed
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants