Feature Overview

As part of XCMSTRAT-613 in ARO-HCP, we want to export the available upgrades for a OCP cluster via a ManifestWork object.

Unfortunately, the ClusterVersionStatus is a somewhat large and complex object, which can only be transported using the rawJSON feedback option.

While working on the feedback rules, we have noticed that the jsonRaw type in the manifestworks CRD has a hardcoded maxLength of 1024 characters.

On the agent side, this limit can be configured [1][2], but it does not reflect on the CRD. Meaning: you can configure a higher limit on the Agent, but the respective field would get rejected by the apiserver validation.

[1] https://github.com/open-cluster-management-io/ocm/pull/366
[2] https://github.com/openshift-online/maestro/blob/main/cmd/maestro/agent/cmd.go#L31

Context in Slack: https://redhat-internal.slack.com/archives/C057Y3D4E1J/p1741794264002799

Goals

This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature

• …

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• ...

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?