Chip Zoller
Chip Zoller
We are not going to cover for this behavior. The change we will make in Kyverno 1.10 is to delete the downstream/generated resource is the clone source is deleted and...
Update: We may be extending the `generate.synchronize` field to cover for this scenario. The expected behavior we agreed upon is that when `synchronize: true` then the following events will cause...
For any folks watching this issue, you're encouraged to join the Kyverno contributors meeting on March 1st as we will be covering all the proposed changes.
> sounds very reasonable @chipzoller, a quick follow-up on: > > > 1. If the resource responsible for the triggering behavior is changed so that it no longer matches the...
As discussed and agreed upon in the [1 March 2023 Kyverno contributor's meeting](https://zoom.us/rec/share/jm4CCyuqWk9MCZgM5LuJ74JGRacDEq_ljOqXkjgzq9p5uh6R7kp62qTIxmWNvhY.AEam0UvXOk4XbBxM), this behavior will be brought into scope for 1.10 and will take effect when synchronization is enabled.
@realshuting we are closed on this issue now, correct? Can you please link the PR responsible?
RC1 will be available this week.
This seems more a regression than a feature. I'm wondering how risky this would be to add to 1.12.1 rather than waiting for 1.13.
Can you show how this looks, please? Also, can you please sign off on your commits?
Can we stack them vertically rather than horizontally? I think that'd be easier to read.