The issues here is feature parity with version 4.
All the v5 labeled issues don't have to be solved before we release version 5 of the operator.
But we would like to have feature partiy/taken an active decision if we should implement the feature.