Closed jhadvig closed 1 week ago
@jhadvig: This pull request references CONSOLE-4265 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.
Hello @jhadvig! Some important instructions when contributing to openshift/api: API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.
@spadgett thank you for the review. I've address the comments. PTAL
@spadgett thank you for the review. Addressed your comments in the additional commit. PTAL
/assign @JoelSpeed
@jhadvig: This pull request references CONSOLE-4265 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.
Thanks, @jhadvig. I agree with the approach and appreciate the detailed doc. Let's have @JoelSpeed take a look 👍
@JoelSpeed thank you for the comments. Addressed them in a separate commit and replied to some of them. PTAL
@JoelSpeed comments addressed. PTAL
@JoelSpeed addressing most of the comments. The only missing piece is the size of the directives, size this will only handle a since ConsolePlugin CR and there could be multiple running on the server.
Adding generated CRD schema + integration test.
PTAL
note: Ive accidentally forced pushed the change... sorry :-/
/retest
@spadgett @JoelSpeed Ive addressed the last comment and squashed the commits. PTAL
/retest
/lgtm
/retest-required
Remaining retests: 0 against base HEAD d37bb9f7e38019b6cfc16f568ee61ffc402c5e9b and 2 for PR HEAD a04311b4b35116b35506bbeee343dfe8cb9284ef in total
/retest
/test e2e-aws-serial
/lgtm /override ci/prow/verify-crd-schema
Only errors refer to unfixable errors or those in the v1alpha1 schema which is meant to have been dropped by now
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jhadvig, JoelSpeed
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema
/retest-required
Remaining retests: 0 against base HEAD d37bb9f7e38019b6cfc16f568ee61ffc402c5e9b and 2 for PR HEAD 424692fe047ee7bd98a690ce93d73108ce65f5c5 in total
/retest-required
Remaining retests: 0 against base HEAD 051d53359b9582b786a12a38f697b10282d126f9 and 1 for PR HEAD 424692fe047ee7bd98a690ce93d73108ce65f5c5 in total
/retest
/retest-required
Remaining retests: 0 against base HEAD e22f17d9b7f5b1785ce6ad2075d0e6ac88f211af and 0 for PR HEAD 424692fe047ee7bd98a690ce93d73108ce65f5c5 in total
/hold
Revision 424692fe047ee7bd98a690ce93d73108ce65f5c5 was retested 3 times: holding
/test e2e-aws-serial
/hold cancel
/override ci/prow/verify-crd-schema
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema
/retest-required
Remaining retests: 0 against base HEAD e22f17d9b7f5b1785ce6ad2075d0e6ac88f211af and 2 for PR HEAD 424692fe047ee7bd98a690ce93d73108ce65f5c5 in total
@jhadvig: all tests passed!
Full PR test history. Your PR dashboard.
[ART PR BUILD NOTIFIER]
Distgit: ose-cluster-config-api This PR has been included in build ose-cluster-config-api-container-v4.18.0-202411092139.p0.ga2817b8.assembly.stream.el9. All builds following this will include this PR.
When serving Console HTML index page, we generate the policy that includes allowed (trustworthy) sources. It may be necessary for some dynamic plugins to add new sources in order to avoid CSP violations at Console runtime. We need to extend the ConsolePlugin CRD, in order to give the plugin creators a mechanism how to specify these source.
We discussed with @vojtechszocs two possible implementation:
Add a new field to spec for specifying an array of sources which would apply for all the CSP directives -
spec.csp.allowedSources
. This implementation is pretty straight-forward but automatically applying the same source across different directives could unintentionally block legitimate content or reduce security.Example:
(Proposed solution) Add a new field to spec for specifying an array of sources for each of the directives. Letting users manage different whitelists for different types of content, gives them more flexibility in controlling security settings.
Example:
Note: The PR is missing some descriptions and validation and unit tests. Will address those once we align on the API structure.
/assign @spadgett @vojtechszocs
Story: https://issues.redhat.com/browse/CONSOLE-4265