[WIP] Design Doc: Support for kpt Apply-Time-Mutation (ATM) in the Remediator#1724
[WIP] Design Doc: Support for kpt Apply-Time-Mutation (ATM) in the Remediator#1724roland-otta wants to merge 1 commit intoGoogleContainerTools:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @vs-odie. Thanks for your PR. I'm waiting for a GoogleContainerTools member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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/test-infra repository. |
|
thank you for contributing a well thought out proposal and following the design doc pattern! Adding to me review list. Apply time mutations have been a subject of much debate over the years. |
This PR introduces a design document proposing support for kpt Apply-Time-Mutation (ATM) in the Config Sync remediator. Currently, only the applier honors ATM annotations, which can lead to resources being reverted to their unmutated state by the remediator. The proposed change ensures that ATM substitutions are applied consistently during both initial apply and ongoing reconciliation, improving correctness and user experience. The design also references real-world needs for cross-resource value injection, as highlighted in k8s-config-connector Issue #101