-
Notifications
You must be signed in to change notification settings - Fork 431
fix(kueueviz): use wildcard for CORS allowed origins in development mode #6603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
4eebd1b
to
372e915
Compare
372e915
to
7ce5f0c
Compare
7ce5f0c
to
8641475
Compare
6fcb585
to
d92be95
Compare
Would you please help to review it :-) |
cmd/kueueviz/backend/README.md
Outdated
|
||
- A Kubernetes cluster | ||
- Go 1.19+ | ||
- Go 1.24+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it required changes? If not could you please split PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mbobrovskyi
It has been changed :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also other changes in this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC required only changes for about KUEUEVIZ_ALLOWED_ORIGINS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mbobrovskyi
It has been modified
85540ce
to
6d07c90
Compare
/lgtm |
LGTM label has been added. Git tree hash: f1d4e1ae4fbf12ea5379ea9e6a30c58e0c78f9d3
|
// Special case for wildcard origin | ||
if origin == "*" { | ||
return "*", true | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you allow *
only when the mode is development?
Because the wildcard origin is obviously security risk in production.
That is strongly not recommended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tenzen-y
It has been changed :-)
6d07c90
to
b8edbd7
Compare
/release-note-edit
|
/cherry-pick release-0.12 |
@tenzen-y: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: Kay Yan <[email protected]> Co-authored-by: Mykhailo Bobrovskyi <[email protected]>
d685a60
to
6777151
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tenzen-y, yankay The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: 6b736714420583fee3483e14a92caea13e79e471
|
@tenzen-y: #6603 failed to apply on top of branch "release-0.12":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@tenzen-y: new pull request created: #6628 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@yankay Could you manually create a cherry-pick PR for release-0.12 branch? You can leverage |
/release-note-edit
|
Hello @tenzen-y This issue was introduced in #5992, but the v0.12.x branch doesn't have this code yet, so the issue doesn't exist there either. Reference: https://github.com/kubernetes-sigs/kueue/tree/release-0.12/cmd/kueueviz/backend |
Oh, I see. In that case, we don't need to cherry pick this to release-0.12. Thank you for checking that! |
What type of PR is this?
/kind bug
What this PR does / why we need it:
*
)Which issue(s) this PR fixes:
Fixes #6584
Special notes for your reviewer:
Does this PR introduce a user-facing change?