Bug 2104151

Summary:	[RFE] RGW / beast should use a port from user range but not 443 for ssl
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Matthias Muench <mmuench>
Component:	rook	Assignee:	Blaine Gardner <brgardne>
Status:	CLOSED NOTABUG	QA Contact:	Neha Berry <nberry>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	madam, mmuench, ocs-bugs, odf-bz-bot, tnielsen
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-29 15:22:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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