Setting target release to the active development branch (4.7.0). For any fixes, where required and requested, cloned BZs will be created for those release maintenance streams where appropriate once they are identified.
Setting UpcomingSprint as unable to resolve before EOD
Setting to 4.6.z since we do not track logging in 4.7. Additionally intend to clone into JIRA for resolution in 5.x
Logging 5.x issue https://issues.redhat.com/browse/LOG-1713
not sure how it was concluded that this was fixed, but it was not fixed. The RBAC is still being created using clusterroles/bindings, not NS roles/bindings.
@Ben do you believe this issue is significant enough it warrants back porting through then entirety of open logging releases?
> @Ben do you believe this issue is significant enough it warrants back porting through then entirety of open logging releases? no
Closed DEFERED per #c11. We will fix this in Logging 5.x streams 5.3+
Correction: 5.4+ unless there is some other compelling reason to fix further back