-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
Not Selected
-
-
Overview:
One may encounter a few references to RH ACS when using the community operator in places such as:
- CR schemas documentation is only available, RHACS-branded, on the RH docs portal
- the descriptions of a few fields in the OpenAPI schema of the custom resources
- the UserAgent header used by the operator controller when talking to the kube API server
- (central web UI when generating init bundles or cluster registration secrets - covered by the clone ticket)
We promised to take care of this.
Might have to move to 5.0: https://issues.redhat.com/browse/ROX-33100
Acceptance Criteria:
Ideally no rhacs reference in the community project UX/docs.
- clones
-
ROX-33134 [stretch][community][UI] Improve the operator branding situation
-
- Refinement
-