Description of problem: BZ-backing JIRA https://issues.redhat.com/browse/NETOBSERV-29 For increased type-safety, we can enable strictNullCheck selectively by overriding the global tsconfig file per directory. Note, there is no special thing to test for QE regarding this pull-request, (apart from usual non-regression in network policy creation through the form). It's purely a technical / code issue. How reproducible: n/a
Closing: PR on hold until 4.10
@jtakvori - as we discussed this isn't making it in 4.9, do you want to mark this invalid for 4.9? Or change the version to 4.10 and mark it duplicate of https://issues.redhat.com/browse/NETOBSERV-29?
@jtakvori never mind, I see the target release is changed from 4.9 to 4.10 in here, so it's a duplicate of https://issues.redhat.com/browse/NETOBSERV-29. FWIW NETOBSERV-29 was marked with QEStatus:Not Required, I've verified this based on other tests done in https://issues.redhat.com/browse/NETOBSERV-6. Thanks! BZ won't allow to have duplicate issue link to JIRA, so I'll mark it as won't fix.
Verified as part of testing https://issues.redhat.com/browse/NETOBSERV-6 and https://issues.redhat.com/browse/NETOBSERV-29
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056