Bug 2267697

Summary:	Document one-liner description about "ux-backend-server" pod introduced from 4.14.5 (4.14, 4.15 docs and above)
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Neha Berry <nberry>
Component:	documentation	Assignee:	Anjana Suparna Sriram <asriram>
Status:	NEW ---	QA Contact:	Neha Berry <nberry>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.14	CC:	assingh, odf-bz-bot
Target Milestone:	---
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:		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:

Description Neha Berry 2024-03-04 14:01:30 UTC

Describe the issue:
=====================

As part of the provider/client changes, a new pod "ux-backend-server". was introduced in all the modes of deployment.

Current work of the pod:  ux-backend-server is designed keeping in mind that in future we can add more API in it.  Right now  its only for onboarding token

Details from slack thread - https://ibm-systems-storage.slack.com/archives/C06DWD30QTZ/p1709285748729949

ux-backend pod should be always deployed! it is a general purpose server pod for UI operations that cannot be implemented by querying metrics or operating directly on k8s resources. It was designed as such and that was the agreement between the UI team and ours. Right now the only operations implemented there are provider released operations  there are already discussions about adding additional non provider related there.
There are no plans right now to gate this pod under a flag and such work was not captured in the design or taken under consideration or effort planning

Describe the task you were trying to accomplish:
==================================================
Add the `ux-backend-server` pod and its basic description in the 4.14 and 4.15 and above deployment or any other relevant guides where we mention about all the deployed pods

It would be good to skip mentioning provider/client specific usage till it is GA'd in 4.16


Suggestions for improvement:

Document URL:

Chapter/Section Number and Title:

Product Version:

Environment Details:

Any other versions of this document that also needs this update:

Additional information: