Pasquale Congiusti
Pasquale Congiusti
More than a bug I think it's the way it is actually designed. I'd mark this issue as an enhancement instead. In any case I'm not sure how we should...
Then, maybe this is not affecting the Pod execution at all. Do you have any failing example, ie, when adding or removing a service without affecting anything else?
Okey. Indeed, it's because the env template vars in pod changes. I've checked and it seems this var is not really used anywhere. I'll try to remove it at all...
I had a look at this and the "problem" is that we use the digest as a mean to compare the previous status of the Integration with the actual one...
> * we can optionally compute the digest of the previous and current object in the event filter (i.e. when the generation or phase have changed we don't have to...
> is it true that if i.e. a deployment changes then we go to the same filter as the Integration resource ? it seems to be odd Yes. If you...
> I know that a reconciliation is triggered but does the integration filter apply ? because if so, then the previous and current integration object would have been the same...
While working on #5491 I realized there is a very important downside of this way to detect a drift. We cannot change the calculation algorithm itself without creating a disruption...
Is this still relevant today? I wonder if with the recent cleaning on Knative trait, this has cleared as well. Any possible way to double check please?
This is interesting. Never seen that though :/