Open oscerd opened 1 month ago
We need to do the change in a backward compatible way. Remind that, although the parameter may not be longer used after Camel 4.7.0, the operator can still run previous runtimes version which are making use of that parameter. I think the best approach is to deprecated and eventually remove when we bump to a major Kubernetes API upgrade.
Requirement
https://issues.apache.org/jira/browse/CAMEL-20775
We need to remove the engine property, since it's not used anymore.
Problem
We need to remove the engine property, since it's not used anymore.
Proposal
Align once we support Camel 4.7.0
Open questions
No response