Bug 2316928 - For external cluster, create a configmap for non secure flags output
Summary: For external cluster, create a configmap for non secure flags output
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.18
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Praveen M
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-07 11:17 UTC by Parth Arora
Modified: 2024-10-07 11:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rook rook pull 14786 0 None open script: add non-secured data 2024-10-07 11:19:14 UTC
Red Hat Issue Tracker OCSBZM-9324 0 None None None 2024-10-07 11:18:16 UTC

Description Parth Arora 2024-10-07 11:17:48 UTC
Description of problem (please be detailed as possible and provide log
snippests):


Currently all the secured and non-secured information is dumped at one place,

So if any nonsecured information is needed for debugging like endpoints details, which cant be made available through logs,
So segregate the secured and the non secured items in the JSON blob

https://github.com/rook/rook/issues/14183



Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.