Bug 2104151 - [RFE] RGW / beast should use a port from user range but not 443 for ssl
Summary: [RFE] RGW / beast should use a port from user range but not 443 for ssl
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Blaine Gardner
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-05 16:32 UTC by Matthias Muench
Modified: 2023-08-09 17:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-29 15:22:00 UTC
Embargoed:

Attachments (Terms of Use)

Comment 3 Blaine Gardner 2022-07-11 17:47:27 UTC 
@mmuench could you provide a bit more information about your request?

Are you specifically concerned about the port on the `rook-ceph-rgw-*` pod itself? Is this regarding the Kubernetes Service?

It sounds like there is no error with usage. What is the specific concern with using port 443? Can you provide documentation for background?
For example, is this violating some security guideline you can provide a document for?
Comment 4 Travis Nielsen 2022-07-25 15:14:45 UTC 
Matthias Any more context for this BZ or shall we close it?
Comment 6 Travis Nielsen 2022-08-29 15:22:00 UTC 
Keeping the existing behavior
Note You need to log in before you can comment on or make changes to this bug.