nifikop
nifikop copied to clipboard
Update NiFi configuration in nifikop for NiFi 2.0.0
Is your feature request related to a problem?
No
Describe the solution you'd like to see
Update all of the various existing NiFi property templates maintained in nifikop for NiFi 2.0.0. This would include things like nifi.properties
, logback.xml
, bootstrap.properties
, bootstrap-notifications.xml
, etc.
Describe alternatives you've considered
No response
Additional context
No response
+1
+1 apache/nifi:2.0.0-M2 has been released.
Are y'all still planning on updating the nifi configuration files for the NiFi 2.0.0 milestones?
+1 apache/nifi:2.0.0-M2 has been released.
Are y'all still planning on updating the nifi configuration files for the NiFi 2.0.0 milestones?
@juldrixx : Do you think it's worth maintaining two branches in nifikop, for example how Apache NiFi team does, for 2.0.0?
+1 apache/nifi:2.0.0-M2 has been released. Are y'all still planning on updating the nifi configuration files for the NiFi 2.0.0 milestones?
@juldrixx : Do you think it's worth maintaining two branches in nifikop, for example how Apache NiFi team does, for 2.0.0?
And if people want to use a 1.X version, they'll have to use an older version of the compatible operator.PPaByPark Because otherwise there's a risk that the operator's functionalities will diverge too much, resulting in 2 completely different versions. What's more, version 1.X will no longer be updated, so we'd have to maintain a version of the operator for a version of NiFi that's no longer evolving, when people should just migrate to a newer version of NiFi.
I am currently upgrading my nifi helm chart 1.26 to nifi 2.0.0-M3 at work. I was thinking whether I should just switch to the nifikop operator instead. Do you have a timeline when nifikop will support nifi 2.00?
I am currently upgrading my nifi helm chart 1.26 to nifi 2.0.0-M3 at work. I was thinking whether I should just switch to the nifikop operator instead. Do you have a timeline when nifikop will support nifi 2.00?
In 1.8.0
the operator is compatible up to 2.0.0-M2
. And the current master
is compatible with 2.0.0-M3
(an issue with dataflow deployment from NiFi Registry).
So in the next release (1.9.0
I guess). I will be compatible up to the latest release 2.0.0-M3
. But you can use the master image if you can't wait.