Skip to content

Conversation

@edmondceausu
Copy link

@edmondceausu edmondceausu commented Feb 3, 2025

What type of PR is this?
/kind feature

What this PR does / why we need it:

Added support for resolveConflicts.PRESERVE (API Reference). This is helpful if users are migrating an existing cluster to Cluster API and do not have their existing Addon Configs specified, or if an out of band change is made to an Addon (eg. configMap change) and the user wants to preserve it.

The schema for conflictResolution had listed none as the default behavior. I updated the docs and code to reflect that.
*
Special notes for your reviewer*:

Checklist:

  • squashed commits
  • includes documentation
  • includes emoji in title
  • adds unit tests
  • adds or updates e2e tests

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Feb 3, 2025
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 3, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@k8s-ci-robot
Copy link
Contributor

Welcome @edmondceausu!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 3, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @edmondceausu. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Feb 3, 2025
@edmondceausu edmondceausu changed the title Addons: Add functionality for resolveConflicts: PRESERVE ✨ Addons: Add functionality for resolveConflicts: PRESERVE Feb 3, 2025
@nrb
Copy link
Contributor

nrb commented Feb 4, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 4, 2025
@nrb
Copy link
Contributor

nrb commented Feb 4, 2025

Thanks for this!

Overall, this looks good to me. The tests are currently failing because make generate needs to be run and the results committed, and it looks like the linter's finding an unnecessary newline.

Once those are fixed (and it passes e2es), I think we're good!

@edmondceausu
Copy link
Author

/retest

@edmondceausu
Copy link
Author

/test pull-cluster-api-provider-aws-test

@richardcase
Copy link
Member

/test pull-cluster-api-provider-aws-e2e

Copy link
Member

@richardcase richardcase left a comment

Choose a reason for hiding this comment

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

Thanks for this @edmondceausu . Just the one small comment.

@edmondceausu edmondceausu force-pushed the addons-preserve branch 2 times, most recently from 924b7be to 925b5d4 Compare April 6, 2025 18:49
@edmondceausu
Copy link
Author

/test pull-cluster-api-provider-aws-e2e

1 similar comment
@damdo
Copy link
Member

damdo commented Apr 10, 2025

/test pull-cluster-api-provider-aws-e2e

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 13, 2025
@richardcase
Copy link
Member

/test ?

@k8s-ci-robot k8s-ci-robot requested review from nrb and richardcase June 16, 2025 10:51
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 16, 2025
@edmondceausu
Copy link
Author

@damdo code has been rebased. Apologies for the delay.

Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

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

Thanks

/lgtm

/assign @richardcase @nrb @AndiDog

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 17, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 67a9048a28dc02ac811bb4bb8ed38d116c7c8a44

@kemv
Copy link

kemv commented Aug 6, 2025

This would fix #5524 🎉

@edmondceausu
Copy link
Author

@AndiDog what do I need to do to get this merged?

@nrb
Copy link
Contributor

nrb commented Aug 6, 2025

/approve

@edmondceausu Thank you for your patience!

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 6, 2025
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 6, 2025
@k8s-ci-robot k8s-ci-robot requested review from AndiDog and damdo August 6, 2025 20:27
@damdo
Copy link
Member

damdo commented Aug 7, 2025

/test pull-cluster-api-provider-aws-e2e-blocking

Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 7, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 4e49ac1edd5756335888c8ed245ee09ad2efbc03

@k8s-ci-robot k8s-ci-robot merged commit 4df1908 into kubernetes-sigs:main Aug 7, 2025
17 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v2.8 milestone Aug 7, 2025
alam0rt pushed a commit to alam0rt/cluster-api-provider-aws that referenced this pull request Sep 4, 2025
…s-sigs#5330)

* Add functionality for resolveConflicts: PRESERVE
fixes for test to pass
removed v1beta1 support

* make generate

* updated documentation and code to reflect kubebuilder behavior

* fixed rebase errors

* make generate after rebase
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. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants